Shorten SAML Request ID and make it hexadecimal, then prepend "id" #23
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
fumieval
force-pushed
the
support-AzureAD
branch
from
32584e8
to
a5ef441
Compare
mbg
reviewed
Oct 24, 2022
fumieval
force-pushed
the
support-AzureAD
branch
from
a5ef441
to
96a6078
Compare
mbg
approved these changes
Oct 26, 2022
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.
Apparently AzureAD has some picky undocumented restriction about the request ID. I reported this to https://github.com/MicrosoftDocs/SupportArticles-docs/issues/763 too.
I confirmed that AzureAD accepts the new format