Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:2.0:single_sign_on:oidc_moodle [2026/09/08 19:00] – [Fields Mapping] kainhoferen:2.0:single_sign_on:oidc_moodle [2026/09/08 19:12] (current) – [Setting up the Client (RP) in Admidio] kainhofer
Line 33: Line 33:
     * Choose an easily understood **label for the client** (only used in Admidio's list of clients, but has no technical use)     * Choose an easily understood **label for the client** (only used in Admidio's list of clients, but has no technical use)
     * Enter the **ClientID from the RP**, copy the created Client Secret (you will later need to paste it indo DokuWiki's configuration), and enter the **Redirect URI** for the RP. Typically the latter can be found either on the RP's configuration page or in the documentation.     * Enter the **ClientID from the RP**, copy the created Client Secret (you will later need to paste it indo DokuWiki's configuration), and enter the **Redirect URI** for the RP. Typically the latter can be found either on the RP's configuration page or in the documentation.
-    * Many open source OIDC clients do not support encryption (PKCE, which is a security mechanism that prevents attackers from obtaining access unless their application started the initial login). By default, PKCE is required by Admidio, so in this case make sure that the requirement checkbox is turned off. Otherwise you will get an error. +    * Moodle'OIDC clients does not support encryption (PKCE, which is a security mechanism that prevents attackers from obtaining access unless their application started the initial login). By default, PKCE is required by Admidio, so make sure that the requirement checkbox is turned off. Otherwise you will get an error. 
   * In Admidio, map the user ID, username, email and fullname to fields that are included in the OpenID login response (so-called "claims") and enter the corresponding claim names in Moodle.    * In Admidio, map the user ID, username, email and fullname to fields that are included in the OpenID login response (so-called "claims") and enter the corresponding claim names in Moodle. 
  
Line 67: Line 67:
   * The **Client Name** is the label of the client in Admidio's client list, it can be anything you like.   * The **Client Name** is the label of the client in Admidio's client list, it can be anything you like.
   * The **"Client ID"** and **"Client Secret"** in Admidio and Moodle have to match exactly. The ID is typically the client's URL, although some clients allow any unique identifier. The Client Secret should a random string and will serve like a password. Admidio will create one and allow it to be copied to the client. Afterwards it is only stored as a hash in the database and not be recovered any more. However, one can create a new Client Secret in Admidio and copy that to the client's configuration.   * The **"Client ID"** and **"Client Secret"** in Admidio and Moodle have to match exactly. The ID is typically the client's URL, although some clients allow any unique identifier. The Client Secret should a random string and will serve like a password. Admidio will create one and allow it to be copied to the client. Afterwards it is only stored as a hash in the database and not be recovered any more. However, one can create a new Client Secret in Admidio and copy that to the client's configuration.
 +  * Moodle's OIDC plugin does not support PKCE, so it must be disabled for the OIDC client in Admidio to prevent errors.
   * Enter the **scopes** you desire in the Moodle config and make sure that Admidio's config matches it. At least **openid must be included** (Admidio will implicitly add it). If group support is desired, the "groups" scope must be included (and the corresponding groups claim mapped, and group support selected in the Moodle config).   * Enter the **scopes** you desire in the Moodle config and make sure that Admidio's config matches it. At least **openid must be included** (Admidio will implicitly add it). If group support is desired, the "groups" scope must be included (and the corresponding groups claim mapped, and group support selected in the Moodle config).
  
 Now save the Identity Provider Settings in Moodle and return to the general OpenID connect settings of the plugin (''https://[YOUR_MOODLE]/admin/category.php?category=oidcfolder''). Now save the Identity Provider Settings in Moodle and return to the general OpenID connect settings of the plugin (''https://[YOUR_MOODLE]/admin/category.php?category=oidcfolder'').
  
-  * Moodle will display its **Redirect URL** in the "Basic settings" section that must be entered in Admidio's settings. Enter this URL in Admidio.{{ :en:2.0:sso:sso_moodle_oidc_04_plugin_settings.png?direct&800 |}}+  * Moodle will display its **Redirect URL** in the "Basic settings" section that must be entered in Admidio's settings. Enter this URL in Admidio.{{ :en:2.0:sso:sso_moodle_oidc_04_plugin_settings.png?direct&600 |}}{{ :en:2.0:sso:sso_moodle_oidc_04_plugin_settings_redirecturl.png?600 |}}
   * Most of the other options can be used for fine-tuning, but in most cases do not need to be changed.   * Most of the other options can be used for fine-tuning, but in most cases do not need to be changed.
  
  • en/2.0/single_sign_on/oidc_moodle.1788886844.txt.gz
  • Last modified: 2026/09/08 19:00
  • by kainhofer