Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -365,7 +365,7 @@ in `Samly.Subject.in_response_to` field. It is the responsibility of the consumi
> will reject (`access_denied`) IdP responses using `SHA1`.
+ `esaml` provides additional checks such as trusted certificate verification, recipient verification among others.
+ By default, `Samly` signs the SAML requests it sends to the Identity Provider. It also
expects the SAML reqsponses to be signed (both assertion and envelopes). If your IdP is
expects the SAML responses to be signed (both assertion and envelopes). If your IdP is
not configured to sign, you will have to explicitly turn them off in the configuration.
It is highly recommended to turn signing on in production deployments.
+ Encrypted Assertions are supported in `Samly`. There are no explicit config settings for this. Decryption happens automatically when encrypted assertions are detected in the SAML response.
Expand Down