-
Notifications
You must be signed in to change notification settings - Fork 6k
Add JdbcRelyingPartyRegistrationRepository #16012
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
Comments
Thanks for the suggestion, @sasirekha98. Are you interested in supplying a PR for this? You can look at the various |
@jzheaux May i work on this? |
Closes spring-projectsgh-16012 Signed-off-by: amirelgayed <[email protected]>
Sorry that I missed you, @wapkch. Are you still interested in working on this? If so, please comment here and feel free also to proceed with a PR. |
@jzheaux Yes, I would be happy to work on this. I’ll proceed with the PR shortly. |
Closes spring-projectsgh-16012 Signed-off-by: chao.wang <[email protected]>
I have an application where the SP metadata is generated as XML and put in the database. We pull the XML and generate the authentication request. When I want to move to Spring Security, I don't find the same option where I can get the relying party details from the data source or directly provide the XML file location.
Currently, as per my understanding, we have the option to load the XML file of the IDP through metadata locations through spring security like this
RelyingPartyRegistrations
.fromMetadataLocation(oktaMetadataUrl)
.registrationId("okta")).build();
Similar to that, it would be nice to have an option where we can load the relying party details when we have them in the database or some location already. We just need to load that file instead of adding the details one by one to the RelyingpartyRegistration.
it will be easier if I have an option where I have to mention the metadata location of the sp as well like this
RelyingPartyRegistrations
.fromMetadataLocationofSP(location)
.fromMetadataLocationofIDP(oktaMetadataUrl)
.registrationId("okta")).build();
The text was updated successfully, but these errors were encountered: