-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Simplify configuration to use different OpenIdConfiguration per webapp. #7042
Labels
Comments
lachlan-roberts
added a commit
that referenced
this issue
Oct 25, 2021
… name. Signed-off-by: Lachlan Roberts <[email protected]>
lachlan-roberts
added a commit
that referenced
this issue
Nov 4, 2021
Signed-off-by: Lachlan Roberts <[email protected]>
lachlan-roberts
added a commit
that referenced
this issue
Nov 9, 2021
Signed-off-by: Lachlan Roberts <[email protected]>
lachlan-roberts
added a commit
that referenced
this issue
Nov 10, 2021
…f realm name Signed-off-by: Lachlan Roberts <[email protected]>
lachlan-roberts
added a commit
that referenced
this issue
Nov 10, 2021
Signed-off-by: Lachlan Roberts <[email protected]>
lachlan-roberts
added a commit
that referenced
this issue
Nov 23, 2021
…ration Issue #7042 - Allow OpenIdConfiguration to be selected based on realm name
Merged #7043. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently to use different OpenID providers for different webapps you must configure everything in the context xml for each webapp and manually add security handler with
Authenticator
andOpenLoginService
etc.It would be a lot better if this could be simplified if this could be discovered and set up automatically based on realm name. Similar to how the
LoginService
is found by theSecurityHandler
from a bean on the Server.The text was updated successfully, but these errors were encountered: