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

EH: Modify social/source authentication parameters #12607

Open
scheibling opened this issue Jan 9, 2025 · 0 comments
Open

EH: Modify social/source authentication parameters #12607

scheibling opened this issue Jan 9, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@scheibling
Copy link
Contributor

scheibling commented Jan 9, 2025

Is your feature request related to a problem? Please describe.
If I've understood it correctly, when redirecting to an external social/source/fed. provider, all policies along the way are run before the provider is selected, or after the user has been authenticated. There are some features in OIDC that would require those types of policies, for example customizing the the prompt parameter (#9971), modifying the redirect URL on the fly or adjusting scopes based on various parameters

Describe the solution you'd like
There are some possible solutions:

  • Introduce a "post-policy" (via setting)

    • Since the current policies are largely run as pre-policies (before the flow step), introducing the option to add policies pre (same as today)- or post (after execution, pre-redirect in the case of the identification flow with external redirect)-step. This one is a little more general, and would introduce a number of new possibilities
  • Introduce scope mapping for authorization requests

    • The ability to add expression-based scope mappings for authorization requests would also work for this

Describe alternatives you've considered
Writing a full custom policy for the entire OIDC auth processm but that would likely be a pain to maintain in the long run

Additional context
This is tangentially related to #12512 as well, and could resolve it by customizing the auth request to include details about the invitation being used, source flow, etc.

Edit: formatting

@scheibling scheibling added the enhancement New feature or request label Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant