Skip to content
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

JWT_MAX_REFRESH_PERIOD not null bug when login #2047

Open
bbprojectnet opened this issue Oct 16, 2020 · 1 comment
Open

JWT_MAX_REFRESH_PERIOD not null bug when login #2047

bbprojectnet opened this issue Oct 16, 2020 · 1 comment
Labels

Comments

@bbprojectnet
Copy link

Subject of the issue

When JWT_MAX_REFRESH_PERIOD is set (not null), then any login attempt throw Token has expired exception.

Your environment

Q A
Bug? yes
New Feature? no
Framework Laravel
Framework version 7.28.4
Package version 2.0
PHP version 7.4

Steps to reproduce

Set JWT_MAX_REFRESH_PERIOD to any not null value. Try to login with correct credentials:

auth()->attempt($credentials);

Expected behaviour

attempt() method should return \Tymon\JWTAuth\Token.

Actual behaviour

attempt() method throw exception.

Linked issue

Also, i think even if JWT_MAX_REFRESH_PERIOD is null, it's not works as expceted. For example:

JWT_TTL=1
JWT_MAX_REFRESH_PERIOD=null

with that configuration i can't refresh my token after 1min (it should be possible because JWT_MAX_REFRESH_PERIOD is infinite).

@stale
Copy link

stale bot commented Dec 25, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Dec 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant