AltiPlan - SSO: Difference between revisions
Appearance
No edit summary |
No edit summary |
||
| Line 37: | Line 37: | ||
| | | | ||
|https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/region-h/endpoint/descriptor | |https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/region-h/endpoint/descriptor | ||
|- | |||
|Region Sj | |||
| | |||
| | |||
|https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/region-sj/endpoint/descriptor | |||
|- | |- | ||
|Aarhus K | |Aarhus K | ||
Revision as of 13:15, 6 October 2025
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.
- Customers need to know claims to return to us in SMAL follow information in claims having names as stated in the table:
| 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 |
3. We also need a URL containing their metadata