Skip to content

SAML 2 Assertion - Always require signature validation #7490

New issue

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

Closed
fhanik opened this issue Sep 28, 2019 · 0 comments · Fixed by #7491
Closed

SAML 2 Assertion - Always require signature validation #7490

fhanik opened this issue Sep 28, 2019 · 0 comments · Fixed by #7491
Assignees
Labels
in: saml2 An issue in SAML2 modules type: enhancement A general enhancement
Milestone

Comments

@fhanik
Copy link
Contributor

fhanik commented Sep 28, 2019

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.

@fhanik fhanik added the type: enhancement A general enhancement label Sep 28, 2019
@fhanik fhanik added this to the 5.2.0 milestone Sep 28, 2019
@fhanik fhanik self-assigned this Sep 28, 2019
@jzheaux jzheaux added the in: saml2 An issue in SAML2 modules label Sep 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: saml2 An issue in SAML2 modules type: enhancement A general enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants