You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We could clarify the fact that Policy API would sometimes require Authorization to access the policies/geographies published on it.
Describe the solution you'd like
When looking at the documentation of the Policy API, in the Authorization section, we could change the language there to say that the publication with our without Authorization of polices on the Policy API is at-will for the publishing user.
Is this a breaking change
No, not breaking
Impacted Spec
policy
Describe alternatives you've considered
N/A
Additional context
We have on multiple occasions at Blue Systems had to publish the policies with Authorized access only to implement some of the use-cases requested by our client cities. So we know this is a minor change for the operators, since they would have credentials for other APIs anyway.
The text was updated successfully, but these errors were encountered:
schnuerle
changed the title
Clarify that Policy API can require Authorzation to access the published material
Clarify that Policy API can require Authorization to access the published material
Jul 12, 2024
Is your feature request related to a problem? Please describe.
We could clarify the fact that Policy API would sometimes require Authorization to access the policies/geographies published on it.
Describe the solution you'd like
When looking at the documentation of the Policy API, in the Authorization section, we could change the language there to say that the publication with our without Authorization of polices on the Policy API is at-will for the publishing user.
Is this a breaking change
Impacted Spec
policy
Describe alternatives you've considered
N/A
Additional context
We have on multiple occasions at Blue Systems had to publish the policies with Authorized access only to implement some of the use-cases requested by our client cities. So we know this is a minor change for the operators, since they would have credentials for other APIs anyway.
The text was updated successfully, but these errors were encountered: