From 361ff06704b7e6175e154d4fcbafef396632b48c Mon Sep 17 00:00:00 2001 From: Antoine Lamirault Date: Wed, 27 Nov 2024 15:56:57 +0100 Subject: [PATCH] Fix typo in README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 951068b8..91cb2ddc 100644 --- a/README.md +++ b/README.md @@ -167,7 +167,7 @@ A replay attack is basically try to reuse an intercepted valid SAML Message in o SAML Messages have a limited timelife (NotBefore, NotOnOrAfter) that make harder this kind of attacks, but they are still possible. -In order to avoid them, the SP can keep a list of SAML Messages or Assertion IDs alredy validated and processed. Those values only need +In order to avoid them, the SP can keep a list of SAML Messages or Assertion IDs already validated and processed. Those values only need to be stored the amount of time of the SAML Message life time, so we don't need to store all processed message/assertion Ids, but the most recent ones.