![]() ![]() In this scenario, the scopes available to you include those implemented by the OpenID Connect (OIDC) protocol. To learn more, read OpenID Connect Scopes. In this case, you need to define custom scopes for your API and then identify these scopes so that calling applications can use them. To learn more, read API Scopes.įrom an application, to call an API that has implemented its own custom scopes. To see examples of calling a custom API from an application, read Sample Use Cases: Scopes and Claims In this case, you need to know which custom scopes are defined for the API you are calling. In certain cases, users get to consent to the access being requested. While usually, the scopes returned will be identical to those requested, users can edit granted scopes (both during initial consent and sometimes after, depending on the resource), thereby granting an app less access than it requested.Īs an application developer, you should be aware of this possibility and handle these cases in your app. For example, your app could warn the user that they will see reduced functionality.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |