From 4ee5800ec96714e051d54c77edf99fda8530d7f3 Mon Sep 17 00:00:00 2001 From: Johannes Graf Date: Sat, 26 Mar 2022 19:02:47 +0100 Subject: [PATCH] use okta as registration id looks like `ping` is some registration id used in the past. Closes gh-11034 --- .../ROOT/pages/servlet/saml2/login/authentication-requests.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/modules/ROOT/pages/servlet/saml2/login/authentication-requests.adoc b/docs/modules/ROOT/pages/servlet/saml2/login/authentication-requests.adoc index ba512b5a4a..58de651528 100644 --- a/docs/modules/ROOT/pages/servlet/saml2/login/authentication-requests.adoc +++ b/docs/modules/ROOT/pages/servlet/saml2/login/authentication-requests.adoc @@ -8,7 +8,7 @@ This filter by default responds to endpoint `+/saml2/authenticate/{registrationI For example, if you were deployed to `https://rp.example.com` and you gave your registration an ID of `okta`, you could navigate to: -`https://rp.example.org/saml2/authenticate/ping` +`https://rp.example.org/saml2/authenticate/okta` and the result would be a redirect that included a `SAMLRequest` parameter containing the signed, deflated, and encoded ``.