-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oidc_refresh_access_token_before_expiry? #1111
Comments
@brandonk10 I believe you're right and I think the fix is that |
zandbelt
added a commit
that referenced
this issue
Sep 14, 2023
see #1111; thanks @brandonk10; bump to 2.4.14.4rc0 Signed-off-by: Hans Zandbelt <[email protected]>
we've added end to end tests in our CI/CD environment to confirm that this issue is fixed in 1cf0a98 |
Thanks for the confirmation and the quick commit! I've done some preliminary testing and things are looking good so far. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Discussed in #1109
Originally posted by brandonk10 September 14, 2023
I'm working off current master, and I'm struggling with this function. The way I understand the logic, it's supposed to refresh the token if it's expired, and returns FALSE if there's an error trying to do that - you're either logged out or re-authenticated if that happens.
My problem seems to be here:
if (t_expires > apr_time_now()) return FALSE;
From what I can tell, this is simply trying to skip the refresh if the token hasn't expired(within TTL). In this case, shouldn't TRUE be returned? I might be doing something else wrong, but I get logged out immediately with this logic, and if I flip to TRUE, my logins start falling through to the application again.
This occurs when "logout_on_error" is included in OIDCRefreshAccessTokenBeforeExpiry.
The text was updated successfully, but these errors were encountered: