-
Notifications
You must be signed in to change notification settings - Fork 58
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
issue refreshing token #72
Comments
Updated and cleaned up thread. |
Any ideas/comments? Not having a refresh cookie option (not working for me) means I’ll have to switch to using header option. |
In effort to further debug I changed using This fails with NullPointer exception when session token expires
while this works
where
|
Sad to not be seeing responses, hopefully this project is still going to be supported. |
Thanks for the report, it will take a bit unfortunately before we get some free time to try and debug the issue. One thing that does go faster, though, is if you'd have a PR :) |
I will keeps looking but I haven’t found source of error yet. I thought I’d post as I go along in case it triggers ideas. Time this side is also tight but want to help
…Sent from my iPhone
On Jun 17, 2021, at 2:44 AM, Adam Warski ***@***.***> wrote:
Thanks for the report, it will take a bit unfortunately before we get some free time to try and debug the issue. One thing that does go faster, though, is if you'd have a PR :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sure, documenting the discovery process is definitely a good idea :) |
I am using refreshable and cookie options for session handling.
OneOff option works as expected but I am unable to get the refreshable option to work.
Setting session max-age to less than refresh max-age results in session timing (as expected).
If using directive requiredSession and session expires I get the following exception thrown (appears to be thrown by processing of directive:
I see the same behavior if I use directive
optionalSession
.My understanding is that the refreshing of token (if using cookie based continuity) is done behind the scenes with no required interaction - is this correct?
Am I missing something? I assume I must be doing something wrong as I would imagine this issue would have been reported.
The text was updated successfully, but these errors were encountered: