SAML metadata upload

Owner: Lena Fischer · Epic: ENG-1522 · Shipped: Tuesday 18 August · Shaped in Emargen as "SAML metadata upload"

Why

Every depot's switch to single sign-on needed its identity provider's metadata, which the customer's IT sent to support in a ticket and an engineer loaded. Brakeline's rollout showed how easy it is to load the wrong file. Kelderby's IT wanted to do it themselves for 25 depots.

What we built

• In the portal's single sign-on settings, an administrator uploads the metadata file for a depot, or copies it from another depot.
• We check it: well-formed, the right entity ID for the customer's connection, a signing certificate, and that certificate not expired.
• An uploaded file is pending until a test sign-in passes; then it is used. A failing test leaves the old one in place.
• The certificate expiry warnings customers' administrators already get, 60 and 30 days before, now link straight to the upload.

What we left out

• Fetching metadata from the identity provider's address on a schedule.
• Uploading for every depot at once.

Rollout

On for everyone on 18 August. Kelderby uploaded Rotterdam's on 21 August; its test sign-in failed because the file came from Kelderby's test tenant (SUP-1116). The pending state kept it from going live.