Feature #17468
Updated by Tom Clegg about 3 years ago
When we accept an OIDC access token in lieu of an Arvados token for an API call, if the OIDC provider is configured to issue access tokens that are signed JWTs with email/name/exp values, the call we make to the UserInfo API is redundant. We should check whether the incoming token is a JWT, passes validation, and has the exp/name/email claims we need, an expiry time, and if so * skip the call to UserInfo * when caching the token in memory/postgres, use the token's embedded expiry time instead of our default TTL