Update the docs to use assertingparty instead of identityprovider to close #12810 #17081
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bed60ad to
5a56db3
Compare
5a56db3 to
772a4a8
Compare
Spring Boot 2.7 renamed spring.security.saml2.relyingparty.registration.*.identityprovider.* to spring.security.saml2.relyingparty.registration.*.assertingparty.*. Closes spring-projectsgh-12810. Signed-off-by: Danilo Piazzalunga <danilopiazza@gmail.com>
Signed-off-by: Danilo Piazzalunga <danilopiazza@gmail.com>
772a4a8 to
37f72a9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As suggested in issue #12810, this PR updates the documentation to reflect the correct usage of the
assertingpartySpring Boot auto-configuration property instead ofidentityprovider.I also believe that the same documentation examples are missing the
registrationproperty; I added them in a separate commit (but I would gladly either squash the two commits, or create a separate PR entirely).