Prerequisites
What are you trying to do that currently feels hard or impossible?
Today, for JWT validation, it assumes that JWKS validation should be sufficient. However there are some identity providers who require introspection validation on the access_token. Additionally, some identity providers require a client id / client secret are provided as part of the introspection request.
Suggested Solution(s)
- Create a flag which allows users to toggle whether or not they want to force introspection on token validation. Default to false so we can maintain backward compatibility
- Create some environment variables for the client ID and client secret so those values can be passed when performing introspection.
- Adding these should not affect backward compatibility
pr: #3831
Alternatives Considered
No response
Additional Details
No response
Prerequisites
What are you trying to do that currently feels hard or impossible?
Today, for JWT validation, it assumes that JWKS validation should be sufficient. However there are some identity providers who require introspection validation on the access_token. Additionally, some identity providers require a client id / client secret are provided as part of the introspection request.
Suggested Solution(s)
pr: #3831
Alternatives Considered
No response
Additional Details
No response