We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In some use cases, privately exchanged credentials can justify a use case where encryption is validation of the assertion content.
The default behavior should be that signature is always required, as that is the most secure behavior.
The text was updated successfully, but these errors were encountered:
Always require signature on either response or assertion
b2ccbc1
Fixes spring-projectsgh-7490 spring-projects#7490
7adb4da
Fixes gh-7490 #7490
fhanik
Successfully merging a pull request may close this issue.
In some use cases, privately exchanged credentials can justify a use case where encryption is validation of the assertion content.
The default behavior should be that signature is always required, as that is the most secure behavior.
The text was updated successfully, but these errors were encountered: