If an OIDC request is made with an expired access token but the id token is unexpired then the request is allowed
Steps to reproduce the bug
Configure a Route w/OIDC configured
Configure the provider so that the access token has a smaller expiration time than the id token (e.g. Okta as the Okta id token expiration is hardcoded to 60 mins)
Send a request and go through the OIDC flow
Wait until the access token has expired but before the id token has expired
Note the request is still accepted
Expected Behavior
When the access token has expired (and there is no refresh or the refresh has expired) then the request should be rejected and redirect back to the IdP
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Gloo Edge Version
1.13.x (latest stable)
Kubernetes Version
None
Describe the bug
If an OIDC request is made with an expired access token but the id token is unexpired then the request is allowed
Steps to reproduce the bug
Expected Behavior
When the access token has expired (and there is no refresh or the refresh has expired) then the request should be rejected and redirect back to the IdP
Additional Context
No response