The SAML response should be a well-formed XML document #26
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
dizzzz
approved these changes
Oct 2, 2023
…ot a fragment. Additionally there is a current bug in eXist-db whereby if the SAML response includes an XML Declaration then fn:parse-xml-fragment#1 will throw an incorrect error.
adamretter
force-pushed
the
hotfix/parse-response
branch
from
a2b1d88
to
787a237
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.
The SAML response should be a well-formed XML document and not a fragment, so we should not try and parse it as a fragment.
Additionally there is a current bug in eXist-db whereby if the SAML response includes an XML Declaration then
fn:parse-xml-fragment#1will throw an incorrect error, for example the following valid XQuery raises an error in eXist-db: