Skip to content

Improve SAML replay docs #784

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.

Sign up for GitHub

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

Open
joshwetzel wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Improve SAML replay docs #784

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
9 changes: 6 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,9 +57,12 @@ We created a demo project for Rails 4 that uses the latest version of this libra
potential security vulnerability, due to its dependency on Nokogiri. Such warnings can
be ignored; Ruby SAML uses Nokogiri in a safe way, by always disabling its DTDLOAD option
and enabling its NONET option.
- **Prevent Replay attacks:** A replay attack is when an attacker intercepts a valid SAML
assertion and "replays" it at a later time to gain unauthorized access. The `ruby-saml`
library provides the tools to prevent this, but **you, the developer, must implement thecore logic**, see an specific section later in the README.
- **Prevent Replay attacks:** A replay attack occurs when an attacker intercepts
a valid SAML assertion and reuses it to gain unauthorized access. The
`ruby-saml` library provides tools to help mitigate this risk, but **it is
your responsibility to implement the necessary logic.** See
[Preventing Replay Attacks](#preventing-replay-attacks) for additional
guidance.


### Supported Ruby Versions
Expand Down