Differences

This shows you the differences between two versions of the page.

--- en:2.0:single_sign_on:oidc_mediawiki [2026/09/08 16:57] – [Prerequisites] kainhofer
+++ en:2.0:single_sign_on:oidc_mediawiki [2026/09/08 17:58] (current) – [Caveats and Things to Consider] kainhofer
@@ Line 16: / Line 16: @@
 The page https://admidio.local/adm_program/modules/preferences.php?panel=sso also provides the link to the automatic discovery URL, and the individual settings for clients that do not support auto-configuration via metadata.
-===== TL;DR; - Quick Overview =====
+===== Quick Overview =====
-Setting up a client (OpenID "Relying Party" - short RP) to use Admidio's user accounts for logging in consists of two steps: (1) The client (RP, MediaWiki in our case) needs to be set up with the data about the OpenID Provider (OP). Typically this is done via the metadata provided in the discovery URL of the provider. Otherwise one has to manually paste the endpoint URLs of the OpenID provider. Since Admidio provides those URLs with copy buttons in the preferences screen, even the manual configuration is rather straigtforward. (2) Admidio needs to be told about the client. In particular, the entity ID and the redirect URL must be given, and a custom-generated (random) secret must be copied to the client configuration.
+Setting up a client (OpenID "Relying Party" = "RP") to use Admidio's user accounts for log-in consists of two steps:
+  - The client (RP, DokuWiki in our case) needs to be set up with the data about the OpenID Provider (OP). Typically this is done via the metadata provided in the discovery URL of the provider. Otherwise one has to manually paste the endpoint URLs of the OpenID provider. Since Admidio provides those URLs with copy buttons in the preferences screen, even the manual configuration is rather straightforward.
+  - Admidio needs to be told about the client. In particular, the entity ID and the redirect URL must be given, and a custom-generated (random) secret must be copied to the client configuration.
 The concrete steps are:
@@ Line 86: / Line 88: @@
         'clientsecret' => 'RkMS+6tlpQQ5yow5PlQQTFRcOMC0XCU/',
         'scope' => ['openid', 'email', 'profile', 'address', 'phone', 'groups', 'custom'],
-        'authMethods' => ['client_secret_post']
+        'authMethods' => ['client_secret_post'],
+        'codeChallengeMethod' => 'S256'
      ],
      'groupsyncs' => [
@@ Line 118: / Line 121: @@
 This is a typical configuration of the MediaWiki OpenID client in Admidio:
 {{ :en:2.0:sso:sso_oidc_mediawiki_02_client.png?direct&600 |}}
+{{ :en:2.0:sso:sso_oidc_mediawiki_02_client2.png?direct&600 |}}
 The clientID and the client secret in the Admidio client page and MediaWiki's ''LocalSettings.php'' 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 MediaWiki, make sure to include the 'groups' scope in Admidio and Mediawiki, and map the 'Roles - roles' Profile Field to an OIDC claim.
@@ Line 134: / Line 138: @@
 ==== Caveats and Things to Consider ====
-  * MediaWiki allows **admin login** through OpenID by assigning the **group 'sysop'** in the group mapping. The 'groups' scope must be included in both Admidio's as well as MediaWiki's config, and Admidio's role must be included as an OIDC claim.
+  * MediaWiki allows **admin login** through OpenID by assigning the **group 'sysop'** in the group mapping. The 'groups' scope must be included in both Admidio's as well as MediaWiki's config, and Admidio's role must be included as an OIDC claim.<code php>[...,
+'groupsyncs' => [
+     [
+         'type' => 'syncall',
+         // List of locally managed groups by default contain 'sysop',
+         // so administrators would never sync from Admidio -> clear it!
+         'locallyManaged' => [],
+         'groupAttributeName' => 'groups',
+     ]]
+</code>{{ :en:2.0:sso:sso_oidc_mediawiki_02_client3_sysop.png?400 |}}
   * By default, MediaWiki will use basic http authentication for its calls to the authorization and token endpoints, which means that no special characters (in particular colons) are allowed. Unfortunately, the  client ID will be used as username, which typically contains a colon in 'https://...'. The OpenID specification states that the colon is the separator between username and passphrase (client secret), so Admidio will incorrectly assume 'https' to be the username and everything else is the client secret... The two possible solutions are to (1) either not use the full URL, but any other unique identifier without a colon as clientID, or (2) switch MediaWiki to the 'client_secret_post' authMethod in the MediaWiki's ''LocalSettings.php'' configuration file (see the example above, which already contains this fix).