Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
en:2.0:single_sign_on:saml_moodle [2025/05/16 23:50] – kainhofer | en:2.0:single_sign_on:saml_moodle [2025/05/17 00:09] (current) – [Setup completed, test Single-Sign-On] kainhofer | ||
---|---|---|---|
Line 36: | Line 36: | ||
* Install the " | * Install the " | ||
- | {{: | + | {{ : |
- | {{ : | + | {{ : |
* After installing this plugin, go to the plugin list and scroll down to the " | * After installing this plugin, go to the plugin list and scroll down to the " | ||
- | {{ : | + | {{ : |
- | * Go to the plugin' | + | * Go to the plugin' |
* The plugin supports auto-loading of Admidio' | * The plugin supports auto-loading of Admidio' | ||
* The "IdP label override" | * The "IdP label override" | ||
- | * If one wants more than one SAML IdP as user backend, it is possible to configure each IdP with an alias to provide direct login links or tweak the display. Typically, this is not needed, except for special cases.{{ : | + | * If one wants more than one SAML IdP as user backend, it is possible to configure each IdP with an alias to provide direct login links or tweak the display. Typically, this is not needed, except for special cases.{{ : |
- | * The plugin configuration allows the explicit generation of cryptographic certificates / keys for signing and encrypt. Usually the default is sufficient (a key is generated and used by moodle in any case).{{ : | + | * The plugin configuration allows the explicit generation of cryptographic certificates / keys for signing and encrypt. Usually the default is sufficient (a key is generated and used by moodle in any case).{{ : |
- | * The next section in the Moodle plugin configuration screen provides a link to the SP metadata, which (after the plugin config is saved) provides Admidio with all relevant information to configure its connection with Moodle as a SAML2.0 IdP.{{ : | + | * The next section in the Moodle plugin configuration screen provides a link to the SP metadata, which (after the plugin config is saved) provides Admidio with all relevant information to configure its connection with Moodle as a SAML2.0 IdP.{{ : |
* The Entity ID is the most relevant identifier that needs to match in Moodle' | * The Entity ID is the most relevant identifier that needs to match in Moodle' | ||
* The link to the SP metadata can be copied from the link using the right mouse button. Typically it is of the form '' | * The link to the SP metadata can be copied from the link using the right mouse button. Typically it is of the form '' | ||
Line 77: | Line 77: | ||
Towards the end of the configuration screen, a whole section "Data mapping" | Towards the end of the configuration screen, a whole section "Data mapping" | ||
- | {{ : | + | {{ : |
The last section would allow Moodle to act as a SAML IdP, which is not relevant in our case. Enabling IDP means that Moodle' | The last section would allow Moodle to act as a SAML IdP, which is not relevant in our case. Enabling IDP means that Moodle' | ||
- | {{ : | + | {{ : |
Line 89: | Line 89: | ||
Admidio and Moodle should now be set up to use Admidio for logging in to Moodle. The SAML plugin even provides a way to test the plugin configuration: | Admidio and Moodle should now be set up to use Admidio for logging in to Moodle. The SAML plugin even provides a way to test the plugin configuration: | ||
- | {{ : | + | {{ : |
The test settings page allows a test login from Moodle to Admidio without influencing the current session Moodle. If login is successful, the profile data provided by Admidio is displayed. | The test settings page allows a test login from Moodle to Admidio without influencing the current session Moodle. If login is successful, the profile data provided by Admidio is displayed. | ||
- | {{: | + | |
+ | {{: | ||
Once, this dry run is successful, one can attempt a real login through SAML. | Once, this dry run is successful, one can attempt a real login through SAML. | ||
Line 98: | Line 99: | ||
If you log out of Moodle (or open Moodle in an incognito browser window) and go to the Moodle admin location, you should see the login screen with the choice of logging in with password or via SAML. | If you log out of Moodle (or open Moodle in an incognito browser window) and go to the Moodle admin location, you should see the login screen with the choice of logging in with password or via SAML. | ||
+ | |||
{{: | {{: | ||
After choosing SAML login and loggin in with a user from Admidio, you should be logged in to Moodle. | After choosing SAML login and loggin in with a user from Admidio, you should be logged in to Moodle. | ||
- | {{ : | + | {{ : |
Line 108: | Line 110: | ||
==== Caveats and Things to Consider ==== | ==== Caveats and Things to Consider ==== | ||
- | * Transferring the country profile field from Admidio into Moodle' | + | * Transferring the country profile field from Admidio into Moodle' |
- | * If you have user accounts from different backends (e.g. local accounts, OpenID Connect login, SAML login) and an account for a user was already created, Moodle tries to match accounts by username (the field selected in the plugin config). However, if the other account has the same email address, but a different user ID through the OIDC or local backend, Moodle will try to create a new account with the SAML user ID, but fails since another account with the same email already exists.{{ : | + | * If you have user accounts from different backends (e.g. local accounts, OpenID Connect login, SAML login) and an account for a user was already created, Moodle tries to match accounts by username (the field selected in the plugin config). However, if the other account has the same email address, but a different user ID through the OIDC or local backend, Moodle will try to create a new account with the SAML user ID, but fails since another account with the same email already exists.{{ : |