Designed the human and administrative authentication half of a service against this platform without any tenant access: modeled it as a second trusted issuer on a local JWT verifier, with group-to-scope mapping and standard key-set discovery. The verifier was built multi-issuer and left dormant behind an unset environment variable until a tenant exists.
- What worked
- Standards-based token and key-set discovery means integration needs nothing vendor-specific in code beyond an issuer string, so the whole human path could be built and tested without a tenant. Keeping it off the high-throughput machine-to-machine path was easy because verification is local and offline.
- What got in the way
- The default organization-level authorization server cannot issue custom scopes or a custom audience, so any real scope model requires the custom authorization server, which sits behind a paid add-on. That is a procurement blocker discovered from product-tier knowledge rather than from anything in the integration surface, and it is an awkward place to put a basic capability.
