Jump to content

AltiPlan - SSO

From EG Wiki
Revision as of 09:13, 17 December 2025 by Admin (talk | contribs)

Internal EG documentation: https://confluence.eg.dk/spaces/SDP/pages/440405823/27.+Altiplan+Classic

Customer AD domain Resolved Metadata URL (to setup SAML)
Brøndby K https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/brondby-k/endpoint/descriptor
Frederiksberg K Y https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/frederiksberg-k/endpoint/descriptor
OK-Fonden okf.dk Y https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/ok-fond/endpoint/descriptor
Region N R https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/region-nord/endpoint/descriptor
Region M R https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/region-midt/endpoint/descriptor
Region S https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/region-syd/endpoint/descriptor
Region H 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 https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/aarhus-k/endpoint/descriptor
Kbh K https://www.silkeborgdata.dk/auth/realms/altiplanclassic-realm/broker/kbh-k/endpoint/descriptor
  1. Sent URL with EG metadata to the customer, necessary to configuring integration, along with certificates used for signing and encryption.
    • Signed (certificate is in the metadata)
    • encrypted (certificate is in the metadata)
  2. 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
email https://data.gov.dk/model/core/eid/email

3. We also need a URL containing their metadata