[docs] Update ADFS configuration #316
Merged
Conversation
This file contains 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
This updates the ADFS configuration to leverage importing the XML metadata both in Jenkins and in ADFS allowing the setup to be simplified. This also adds some additional details around attributes to be configured in Jenkins and what to set in ADFS to receive them. Signed-off-by: Ben Magistro <[email protected]>
bmagistro
force-pushed
the
update-adfs-docs
branch
from
e3468c2 to
7625953
Compare
kuisathaverat
approved these changes
Mar 2, 2023
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.
This updates the ADFS configuration to leverage importing the XML metadata both in Jenkins and in ADFS allowing the setup to be simplified. This also adds some additional details around attributes to be configured in Jenkins and what to set in ADFS to receive them.
Open to image resize/formatting suggestions
While configuring SAML I found the SP metadata at a different URL, specifically
manage/securityRealm/metadata. Based on the information in CONFIGURATION.md I am assuming this is an artifact of how Jenkins is serving/exposing these files.