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
When creating a resource server, you must provide a resource server name and a resource server identifier. For each scope you create in the resource server, you must provide the scope name and description.
Resource server name: A friendly name for the resource server, such as Solar system object tracker or Photo API.
Resource server identifier: A unique identifier for the resource server. The identifier is any name that you want to associate with your API, for example solar-system-data. You can configure longer identifiers like https://solar-system-data-api.example.com as a more direct reference to API URI paths, but longer strings increase the size of access tokens.
Scope name: The value that you want in your scope claims. For example, sunproximity.read.
Description: A friendly description of the scope. For example, Check current proximity to sun.
The text was updated successfully, but these errors were encountered:
So if it's just about custom scopes, maybe we're talking about a solved problem?
RD should just register a few custom scopes into SRAM as part of its resource server definition, and done. No need for a plugin framework probably!
So the hard part we're trying to solve is very much related to scopes that are both custom and structured!
I found something in AWS Cognito. Custom scopes instead of dynamic/structured scopes:
https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-define-resource-servers.html
The text was updated successfully, but these errors were encountered: