Preflight Checklist
Problem Description
Dex has an exhaustive list of scopes it supports. These scopes are all defined in the OIDC spec. Many IDPs support additional scopes. In some cases this include dynamic scopes which can change depending on the application or a specific flow. It would be great if Dex can support these additional scopes using an opt-in configuration mechanism.
Proposed Solution
The idea would be to extend the OAuth2 configuration with a list of allowed scope (prefixes). This would allow the Dex operator to still verify the scopes passed by the client to have certain well-known prefixes.
Alternatives Considered
No alternatives exist to support this other than using a non Dex solution.
Additional Information
Created a DEP #2961 for this
Created a PR #2962 with an initial implementation (to be refined further if needed)
Preflight Checklist
Problem Description
Dexhas an exhaustive list of scopes it supports. These scopes are all defined in the OIDC spec. Many IDPs support additional scopes. In some cases this include dynamic scopes which can change depending on the application or a specific flow. It would be great ifDexcan support these additional scopes using an opt-in configuration mechanism.Proposed Solution
The idea would be to extend the
OAuth2configuration with a list of allowed scope (prefixes). This would allow the Dex operator to still verify the scopes passed by the client to have certain well-known prefixes.Alternatives Considered
No alternatives exist to support this other than using a non Dex solution.
Additional Information
Created a DEP #2961 for this
Created a PR #2962 with an initial implementation (to be refined further if needed)