... | ... | @@ -7,6 +7,7 @@ The reg-app needs at least one service provider configured, to function. To add |
|
|
After the configuration is created, you need to edit it. In the textbox "Assertion Consumer Endpoint" you need to enter the URL "https://your-hostname/Shibboleth.sso/SAML2/POST". In the textbox "ECP Endpoint" the value has to be "https://your-hostname/Shibboleth.sso/SAML2/ECP". These values can not be choosen freely for now. This is a planned feature to gain more flexibility for the SAML Subsystem. To complete the configuration, add an entry for the hostname of the system. You can specify more than one, if virtual hosts are involved. When done, click on save, to persist the changes.
|
|
|
|
|
|
| Field | Description | Example value |
|
|
|
|----|----|----|
|
|
|
| Entity ID* | The entity ID of yout SAML Service Provider | `https://<your-hostname>/sp` |
|
|
|
| Assertion Consumer Endpoint* | The assertion consumer endpoint, where the user is redirected after authenticating with the IDP. Can be '/Shibboleth.sso/SAML2/POST', or '/saml/sp/post'. Has to be the same URL that is defined in the federation metadata of the SP. | `https://<your-hostname>/Shibboleth.sso/SAML2/POST` |
|
|
|
| ECP Endpoint* | If you service is using the ECP protocol, this URL has to be set and match the ECP endpoint of the SP in the federation metadata. Most propably, you won't be using this feature. Because of being a mandatory field, it's best just to use the example value. | `https://<your-hostname>/Shibboleth.sso/SAML2/ECP` |
|
... | ... | |