Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore existing auth server plugins that do something like share selection #36

Closed
michielbdejong opened this issue Mar 26, 2024 · 2 comments

Comments

@michielbdejong
Copy link
Collaborator

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

Managing the Resource Server and Custom Scopes

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.

@michielbdejong
Copy link
Collaborator Author

Same for Salesforce, also just scope name and description: https://help.salesforce.com/s/articleView?id=sf.remoteaccess_oauth_customscopes_create.htm&type=5

@michielbdejong
Copy link
Collaborator Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant