AltiPlan - SSO: Difference between revisions
Appearance
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
| | | | ||
|https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/frelsenshaer/endpoint/descriptor | |https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/frelsenshaer/endpoint/descriptor | ||
| | |https://login.microsoftonline.com/6cf97196-9396-42e3-8b3d-41c4c6d52e3d/federationmetadata/2007-06/federationmetadata.xml | ||
|- | |- | ||
|Høje Taastrup K (htk) | |Høje Taastrup K (htk) | ||
Revision as of 12:28, 9 September 2026
Internal EG documentation: https://confluence.eg.dk/spaces/SDP/pages/440405823/27.+Altiplan+Classic

- Sent URL with EG metadata to the customer, necessary to configuring integration, along with certificates used for signing and encryption.
- We require that the communication is:
- Signed (certificate is in the metadata)
- encrypted (certificate is in the metadata)
- Customers need to know claims to return to us in SMAL follow information in claims having names as stated in the table. We also need particular claims - which are also in metadata:
| Attribute | Claim |
| username | https://data.gov.dk/model/core/eid/alias |
| firstName | https://data.gov.dk/model/core/eid/firstName |
| lastName | https://data.gov.dk/model/core/eid/lastName |
| https://data.gov.dk/model/core/eid/email |
4. We also need a URL containing their metadata