-
Notifications
You must be signed in to change notification settings - Fork 232
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
Cookie "expires" is never set #119
Comments
@awhitty - the token expiry is enforced by the server, so the cookies should remain in the browser indefinitely. I did just find this in the ipCookie docs:
I don't remember it working this way initially - I may have built against a version that didn't have this behavior. Thanks for reporting the issue, I'll push a fix ASAP. |
Just checking if this is still imminent. Thanks! |
Hi @Proletarian - I'll push a fix for this tonight. Sorry for the delay. |
Woohoo! No worries. Appreciate the update. On Monday, 18 May 2015, Lynn Dylan Hurley [email protected] wrote:
Best regards, Adeel Ahmad Follow @shopseen everywhere |
Fixed in |
I may be interpreting this the wrong way, but in order for the user's logged-in session to last longer than the browser session, the cookie storing the auth tokens should have an
expires
property. #107 mentions this issue, but the issue was closed, and I do not think it has been adequately addressed.As soon as a user refreshes the page, the user's session and relevant cookies have been lost, forcing the user to reauthenticate.
If it helps, I'm using the email/password authentication scheme.
The relevant code:
You can see that there is no
expires:
in the object passed to ipCookie. Is this the correct behavior?The text was updated successfully, but these errors were encountered: