From 5ff4958423f42fe5cecb7c8e15626c516bb22c05 Mon Sep 17 00:00:00 2001 From: Philippe Perrin Date: Tue, 13 Sep 2022 16:10:02 +0200 Subject: [PATCH] SONAR-17232 Improve SAML documentation --- .../instance-administration/authentication/saml/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/sonar-docs/src/pages/instance-administration/authentication/saml/overview.md b/server/sonar-docs/src/pages/instance-administration/authentication/saml/overview.md index 1122f01ad51..53ff545ab9e 100644 --- a/server/sonar-docs/src/pages/instance-administration/authentication/saml/overview.md +++ b/server/sonar-docs/src/pages/instance-administration/authentication/saml/overview.md @@ -8,7 +8,7 @@ You can delegate authentication to a SAML 2.0 Identity Provider using SAML Authe ## SAML authentication flow 1. When a user requests a SonarQube web page and is not already authenticated, SonarQube will start a SAML authentication process. -2. SonarQube creates a SAML request for the configured Identity Provider and sends it back to the user. +2. SonarQube creates a SAML request for the configured Identity Provider and sends it back to the user's browser. 3. The user's browser automatically relays the SAML request to the Identity Provider. 4. The Identity Provider authenticates the user and creates a SAML assertion containing the user information and privilege. Optionally, it can encrypt this assertion with the SonarQube certificate. 5. The Identity Provider sends a SAML assertion back to the web browser -- 2.39.5