diff options
| author | Philippe Perrin <philippe.perrin@sonarsource.com> | 2022-09-13 16:43:34 +0200 |
|---|---|---|
| committer | sonartech <sonartech@sonarsource.com> | 2022-09-22 20:03:33 +0000 |
| commit | 3eeb15ab739dc67d135128142a37b8c75635a8d1 (patch) | |
| tree | 86e3198b80267842932564217c69008783d450af /server/sonar-docs | |
| parent | 5ff4958423f42fe5cecb7c8e15626c516bb22c05 (diff) | |
| download | sonarqube-3eeb15ab739dc67d135128142a37b8c75635a8d1.tar.gz sonarqube-3eeb15ab739dc67d135128142a37b8c75635a8d1.zip | |
SONAR-17230 Improve Okta documentation
Diffstat (limited to 'server/sonar-docs')
| -rw-r--r-- | server/sonar-docs/src/pages/instance-administration/authentication/saml/keycloak.md | 2 | ||||
| -rw-r--r-- | server/sonar-docs/src/pages/instance-administration/authentication/saml/okta.md | 14 |
2 files changed, 13 insertions, 3 deletions
diff --git a/server/sonar-docs/src/pages/instance-administration/authentication/saml/keycloak.md b/server/sonar-docs/src/pages/instance-administration/authentication/saml/keycloak.md index 58e0b6eea74..4a2070962e3 100644 --- a/server/sonar-docs/src/pages/instance-administration/authentication/saml/keycloak.md +++ b/server/sonar-docs/src/pages/instance-administration/authentication/saml/keycloak.md @@ -5,6 +5,8 @@ url: /instance-administration/authentication/saml/keycloak/ The following content may be useful if you're using Keycloak as a SAML Identity Provider. +To integrate Keycloak (Identity Provider) with SonarQube (Service Provider), both sides need to be configured. + ## Keycloak server configuration Create a new SAML client diff --git a/server/sonar-docs/src/pages/instance-administration/authentication/saml/okta.md b/server/sonar-docs/src/pages/instance-administration/authentication/saml/okta.md index 4b8845ecc77..4e61ab7a19c 100644 --- a/server/sonar-docs/src/pages/instance-administration/authentication/saml/okta.md +++ b/server/sonar-docs/src/pages/instance-administration/authentication/saml/okta.md @@ -6,6 +6,7 @@ url: /instance-administration/authentication/saml/okta/ The following example may be useful if you are using Okta as a SAML Identity Provider. Note that Okta does not support service provider signed requests even if they are enabled on the SonarQube side. +To integrate Okta (Identity Provider) with SonarQube (Service Provider), both sides need to be configured. ## Create a new application in Okta admin dashboard @@ -30,6 +31,14 @@ Under *General Settings*, configure the following fields:  +Assertion signature is mandatory. You must keep the following default settings in *Show Advanced Settings*: + +- **Response**: Choose *Signed*. + +- **Assertion Signature**: Choose *Signed*. + +- **Signature Algorithm**: Choose *RSA-SHA256*. + (Optional) If you want to enable assertion encryption, expand *Show Advanced Settings* and configure the following fields: - **Assertion Encryption**: Choose *Encrypted*. @@ -38,7 +47,7 @@ Under *General Settings*, configure the following fields: - **Key Transport Algorithm**: Choose *RSA-OAEP*. -- **Encryption Certificate**: Add the service provider certificate. It should be the same certificate as that found in the SonarQube SAML settings under "Service provider certificate". +- **Encryption Certificate**: Add the service provider certificate. It should be the same certificate as the one found in the SonarQube SAML settings under "Service provider certificate".  @@ -86,8 +95,7 @@ You can now add users and groups in the *Assignments* tab of the application.  - -After the application creation, navigate to the **Sign On** tab of the *SonarQube* application in Okta. +Navigate to the **Sign On** tab of the *SonarQube* application in Okta.  |