This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |
| en:2.0:single_sign_on:oidc_gitlab [2026/09/08 19:51] – [Setting up the Client (SP) in Admidio] kainhofer | en:2.0:single_sign_on:oidc_gitlab [2026/09/08 19:51] (current) – [Setting up the Client (SP) in Admidio] kainhofer |
|---|
| This is a typical configuration of the GitLab OpenID client in Admidio: | This is a typical configuration of the GitLab OpenID client in Admidio: |
| |
| {{:en:2.0:sso:sso_oidc_gitlab_03_client.png?direct&450|}} | {{:en:2.0:sso:sso_oidc_gitlab_03_client.png?direct&800|}} |
| |
| The clientID and the client secret in the Admidio client page and GitLab's ''config/gitlab.rb'' have to match exactly. Similarly, the scopes should coincide, otherwise not all desired profile fields will be transmitted. To make use of the group mapping in GitLab (see the [[https://docs.gitlab.com/administration/auth/oidc/#configure-users-based-on-oidc-group-membership|Gitlab documentation for details]]), make sure to include the 'groups' scope in Admidio and GitLab, and map the 'Roles - roles' Profile Field to an OIDC claim. | The clientID and the client secret in the Admidio client page and GitLab's ''config/gitlab.rb'' have to match exactly. Similarly, the scopes should coincide, otherwise not all desired profile fields will be transmitted. To make use of the group mapping in GitLab (see the [[https://docs.gitlab.com/administration/auth/oidc/#configure-users-based-on-oidc-group-membership|Gitlab documentation for details]]), make sure to include the 'groups' scope in Admidio and GitLab, and map the 'Roles - roles' Profile Field to an OIDC claim. |
