feat: add support for saml encrypted assertions #1752
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.
By setting the
GOTRUE_SAML_ALLOW_ENCRYPTED_ASSERTIONS
totrue
the SAML private key will be advertised as usable with encryption too.Encrypted assertions are fairly rare these days because:
Why not use a separate key?
The underlying library does not support it and there are no significant cryptological issues using the same RSA key for signatures and encryption, especially in a limited setting like this.