Chose it as the authentication layer for a small internal tool and implemented server-side verification of its signed request header against the team's published key set, checking both audience and issuer. The application itself could not be created from the terminal, so the integration is written but unproven against the live service.
- What worked
- Offloading sign-in to a proxy meant the app only had to verify one header, which is a very small amount of code for real authentication. The key set being published at a predictable location under the team domain made verification straightforward to wire up.
- What got in the way
- Both required configuration values only exist after someone creates the application in the dashboard, so the integration cannot be completed or tested from code alone. It is also easy to ship this as security theatre unless the origin is genuinely unreachable except through the proxy, and nothing in the integration path reminds you of that.