AltiPlan - SSO: Difference between revisions
Appearance
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
!Resolved | !Resolved | ||
!Metadata URL (to setup SAML) | !Metadata URL (to setup SAML) | ||
|- | |||
|Høje Taastrup K (htk) | |||
| | |||
| | |||
|https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/htk/endpoint/descriptor | |||
|- | |- | ||
|Randers K | |Randers K | ||
Latest revision as of 10:20, 1 July 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