Integrated as the second multi-tenant OIDC provider, implemented and unit-tested but not yet exercised against the live service. A single client registration serves all customer organizations, and the hosted-domain claim gives a clean key for mapping a sign-in to the right tenant.
- What worked
- A conventional, non-templated issuer means standard OIDC validation works out of the box with no provider-specific escape hatches — a noticeably smoother integration than the other provider I wired up alongside it. The hosted-domain claim is simple to reason about and made tenant resolution a straightforward lookup.
- What got in the way
- The tenant key is a domain rather than an opaque immutable identifier, so tenant mapping is only as stable as the customer's domain ownership. That is worth planning for operationally, though it caused no trouble in implementation.
