From c36efa96765262b9840163ebed6468a51366bdc4 Mon Sep 17 00:00:00 2001 From: Ryan McAllen <rhyno@rhynodesigns.com> Date: Wed, 11 May 2016 15:21:10 -0400 Subject: [PATCH] Spelling: successfull -> successful (#389) --- docs/simplesamlphp-idp-more.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/simplesamlphp-idp-more.txt b/docs/simplesamlphp-idp-more.txt index 8b4937f6e..fe61e1709 100644 --- a/docs/simplesamlphp-idp-more.txt +++ b/docs/simplesamlphp-idp-more.txt @@ -33,7 +33,7 @@ SimpleSAMLphp has implemented a graceful fallback to tackle this situation. When What happens in the IdP-first flow is that a *SAML unsolicited response* is sent directly to the SP. An *unsolicited response* is a SAML Response with no reference to a SAML Request (no `InReplyTo` field). -When a SimpleSAMLphp IdP falls back to IdP-first flow, the `RelayState` parameter sent by the SP in the SAML request is also lost. The RelayState information contain a reference key for the SP to lookup where to send the user after successfull authentication. The SimpleSAMLphp Service Provider supports configuring a static URL to redirect the user after a unsolicited response is received. See more information about the `RelayState` parameter in the next section: *IdP-first flow*. +When a SimpleSAMLphp IdP falls back to IdP-first flow, the `RelayState` parameter sent by the SP in the SAML request is also lost. The RelayState information contain a reference key for the SP to lookup where to send the user after successful authentication. The SimpleSAMLphp Service Provider supports configuring a static URL to redirect the user after a unsolicited response is received. See more information about the `RelayState` parameter in the next section: *IdP-first flow*. IdP-first flow -- GitLab