Hey @tymondesigns I'm still not able to get a token from the attempt method
Did u make the changes as in #177?
I seem to remember from your snippet that you posted. You had this->url in the getJWTSubject method
This is what the illuminate auth adapter will use to retrieve the authenticated user. So you should change this to $this->id for it to work
Yeah, I had messed up that when trying to figure out the error; but I've since changed url to id; the aforementioned error still persists though!
Hi, if i have a token created from a laravel application with the jwt-auth package. Can verify the token in a microservice with the same jwt-auth package if i have the same secret?
Solved .I had two different versions of jwt-auth package that was causing a signed failed.
@tymondesigns so is Lumen 5.2 officially covered? Seeing a lot of make-it-works in the issues but can't tell if it's now fully covered
Hi everyone !!!
Need support on JWT getting started !!!
I am not able to get started
Hello @mannutech which part do you need help on?
Hi, I was wondering if anyone could clear something up that I'm a bit confused about.
When a user authenticates and gets a token, is the token refreshed every time they make a request? Or do they keep the same token?
You need a local storage concept
If "rememberMe" flag is set by user then in your backend impl you do not set an experation
How can I pass conditions to the login process apart from the user's credentials, I want to pass a condition to check if the user is active, from the active column in the users table
U can add a tenant
Once I add that, how would I pass it to the JWT::attempt()
Thank you @brian-singer
@KR78 decode the token and read the parameter....
I am going to make SPA with larvel and angular js some one here can give me some suggestions from there experience and also using JWT for authentication
I'm working with a SPA with Laravel and AngularJS, it's awesome, I'm using and angularjs package called satellizer which stores the JWT token once a user is authenticated in the localstorage of the browser or as a cookie depending on your preference and sends it's out with every request made to the Laravel API
You can monitor authentication based on the JWT token that's stored using the package, it keeps track of the token and you check if the token has expired with $auth.isAuthenticated() and fire an event like pop up a modal asking them to login again or redirect the user to the login page
Hi guys I have a jwt token setup and im passing through some custom claims like the associated user roles and permission there name and there avatar image... The user could fall under a few permissions though or may have a lot of associated roles.. I am worried about the custom claims bit becoming to big as I have seen warnings that it shouldnt be. So my question is what is the best practice on the size of the custom claims