Include proper KeyName in encrypted assertion #781
Merged
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.
Problem
The IdP encrypted assertions returned by pysaml2 are always associated with the following KeyInfo :
That can make some SPs to not know which one of their keys has been used (even if they specify just one in their metadata, they might perform a check at decryption time).
This PR aims to do the following :
KeyInfo
exists in the SP metadata, noKeyInfo
is associated with the encrypted assertionSolution
(key_name, cert)
All Submissions: