ACME HQDemo work items and pages, made up for Emargen's demo. Not a real company.

Engineering / ENG-1386

Spike: Okta as identity provider for a depot (Vossberg asked)

Project: Engineering
Type: Task
Status: Done Done
Priority: Medium
Organization: Vossberg Logistik
Reporter: Rafael Duarte <rafael.duarte@acme-hq.example>
Assignee: Marek Nowak <marek.nowak@acme-hq.example>
Labels: vossbergokta
Components: identity-service
Sprint: Sprint 40
Created: 15 Apr 2026, 08:20 UTC
Updated: 23 Apr 2026, 15:30 UTC
Resolved: 23 Apr 2026, 15:30 UTC

Description

Vossberg Logistik use Okta and want single sign-on. We say "Entra ID; Okta untested". Test it.

Results with an Okta developer tenant and our per-depot config:

Sign-in works once the depot's config has the Okta app's metadata. One Okta app per depot, as with Entra ID.
Okta sends NameID as unspecified, not emailAddress. We refuse that today.
Okta groups can carry roles the same way Entra ID groups do.
Vossberg would like to send each person's depot code as an attribute, so we can check people sign in at their own depot.

Handing to Lena for shaping.

Linked issues

relates to SUP-817 Vossberg: sign-in with Okta instead of passwords Done

Comments (0)

No comments.