Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
Nächste Überarbeitung		 Vorhergehende Überarbeitung
en:2.0:single_sign_on:oidc_joomla [2026/09/07 17:01] – [Configuring the Service Provider (Joomla)] kainhoferen:2.0:single_sign_on:oidc_joomla [2026/09/08 15:52] (aktuell) – [Caveats and Things to Consider] kainhofer
Zeile 29: Zeile 29:
     * 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 Joomla'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 Joomla'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. 
   * Optionally select (both in Admidio and the RP) which **profile fields should be mapped** to OpenID claims (attributes) and sent to the client, and configure which **group memberships** should be transmitted.   * Optionally select (both in Admidio and the RP) which **profile fields should be mapped** to OpenID claims (attributes) and sent to the client, and configure which **group memberships** should be transmitted.
  
Zeile 69: Zeile 70:
   * The Client Secret should be 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 Secret should be 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 "Redirect URL" in Admidio's config should be the Redirect / Callback URL of Step 1 of the Joomla configuration (typically ''https://[YOUR_INSTALLATION]''){{ :en:2.0:sso:sso_oidc_joomla_05_clientsetup.png?direct&900 |}}   * The "Redirect URL" in Admidio's config should be the Redirect / Callback URL of Step 1 of the Joomla configuration (typically ''https://[YOUR_INSTALLATION]''){{ :en:2.0:sso:sso_oidc_joomla_05_clientsetup.png?direct&900 |}}
 +  * The Joomla OIDC plugin 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. 
   * Enter the **scopes** you desire in Joomla's config and make sure that Admidio's config matches them. At least **openid must be included** (Admidio will implicitly add it). As the free plugin does not support advanced fields mapping or group mappin, only the "email" and "profile" scopes are relevant and should be selected (otherwise the email and username will not be sent to Joomla).   * Enter the **scopes** you desire in Joomla's config and make sure that Admidio's config matches them. At least **openid must be included** (Admidio will implicitly add it). As the free plugin does not support advanced fields mapping or group mappin, only the "email" and "profile" scopes are relevant and should be selected (otherwise the email and username will not be sent to Joomla).
  
Zeile 116: Zeile 118:
   * The free version of the miniOrange plugin is very limited, allowing only login for existing joomla users (with their Admidio passwords at the admidio site). Each user must first be created manually in Joomla!   * The free version of the miniOrange plugin is very limited, allowing only login for existing joomla users (with their Admidio passwords at the admidio site). Each user must first be created manually in Joomla!
   * The free version also does not allow transferring any group information from Admidio to Joomla, or other profile fields.   * The free version also does not allow transferring any group information from Admidio to Joomla, or other profile fields.
-  * Currently, there are no full-featured, free Single-Sign-On solutions for Joomla that support field and group mapping for permissions in Joomla. The miniOrange plugins we described here provide only basic SSO functionality, while the useful features are available only in the paid versions. Given the high costs of these versions and considering the tight budget most non-profit associations face, the paid version is usually way to expensive to even consider...+  * Currently, there are no full-featured, free Single-Sign-On solutions for Joomla that support field and group mapping for permissions in Joomla. The miniOrange plugins we described here provide only basic SSO functionality, while the useful features are available only in the paid versions. Given the high costs of these versions and considering the tight budget most non-profit associations face, the paid version is usually way too expensive to even consider...
  • en/2.0/single_sign_on/oidc_joomla.1788793274.txt.gz
  • Zuletzt geändert: 2026/09/07 17:01
  • von kainhofer