Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
| Beide Seiten der vorigen Revision Vorhergehende Überarbeitung Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
| en:2.0:single_sign_on:saml_wordpress [2025/04/27 22:07] – [Configuring the Service Provider (Wordpress)] kainhofer | en:2.0:single_sign_on:saml_wordpress [2026/09/04 17:05] (aktuell) – [Setting up the Client (SP) in Admidio] kainhofer | ||
|---|---|---|---|
| Zeile 9: | Zeile 9: | ||
| Throughout the document we will assume you have both Admidio and Wordpress already set up properly at https:// | Throughout the document we will assume you have both Admidio and Wordpress already set up properly at https:// | ||
| - | As a first step, one needs to **configure Admidio to act as an SAML 2.0 Identity Provider** (IdP). This has to be done once and is not specific to any client. Please | + | As a first step, one needs to **configure Admidio to act as an SAML 2.0 Identity Provider** (IdP). This has to be done once and is not specific to Wordpress. Please |
| {{ : | {{ : | ||
| - | Basically, one (1) needs to **create a cryptographic key** to sign message | + | Basically, one needs to enable SAML 2.0 and **choose a unique EntityID**. |
| - | The page preferences https:// | + | |
| - | ===== TL; | + | The page https:// |
| - | Setting up a client (SAML " | + | ===== Quick Overview ===== |
| + | |||
| + | Setting up a client (SAML " | ||
| * At the **Service Provider (SP)** - Wordpress in our case - **install the extension** to support SAML login. | * At the **Service Provider (SP)** - Wordpress in our case - **install the extension** to support SAML login. | ||
| Zeile 23: | Zeile 24: | ||
| * Choose whether sent messages **should be signed and/or encrypted** (these features require an additional private key and certificate for the SP!), and whether received messages are checked for signatures or encryption is expected. | * Choose whether sent messages **should be signed and/or encrypted** (these features require an additional private key and certificate for the SP!), and whether received messages are checked for signatures or encryption is expected. | ||
| * In **Admidio**, | * In **Admidio**, | ||
| - | * Choose an easily understood **label for the client** (only used in Admidio' | + | * Choose an easily understood **label for the client** (only used in Admidio' |
| * Enter the **ClientID from the SP**, as well as the ACS URL and the SLO response URL. These values must be provided by the client. | * Enter the **ClientID from the SP**, as well as the ACS URL and the SLO response URL. These values must be provided by the client. | ||
| * In Admidio, also choose whether sent messages should be **signed or encrypted**. The crypto key generated in the general SAML setup will be used. | * In Admidio, also choose whether sent messages should be **signed or encrypted**. The crypto key generated in the general SAML setup will be used. | ||
| Zeile 69: | Zeile 70: | ||
| - | Now, return to Admidio' | + | Now, return to Admidio' |
| {{ : | {{ : | ||
| - | Paste the metadata URL copied from Wordpress into the corresponding input field at the top and click "Load Client Metadata" | + | Paste the metadata URL copied from Wordpress into the corresponding input field at the top and click "Load Client Metadata" |
| {{ : | {{ : | ||
| + | {{ : | ||