jwt-auth VS jwt-auth

First, thank you to everyone who contributed to Tymon's JWT Auth library. I found there were various issues with it (lasagna code, having to extend/override existing functionality, lack of functionality, etc.) that made it challenging to work with, which is what inspired me to create Little JWT.

Due to inactivity by the maintainer, this has forced laravel developers that use php 8, to look for alternatives. Here is a list of alternatives to the tymondesigns/jwt-auth package, that i have managed to find, in my quest to find alternative packages.

I'm not sure if Sanctum is fine for generating tokens because the jwt-auth package seems to be abandoned. For context, I'm used to develop with Laravel plain html, and now I want to separate front-end with Svelte and back-end with Laravel, as because I'm used to it. The questions is: Is it ok to just use Sanctum package? I know it's not really jwt token, but seems to do the job.

Jwt-auth

You can make a login route in api.php and then return the token if you want simpler token for authentication might I suggest that you use jwt token it's simple and it's docs show you how to use the jwt token https://github.com/tymondesigns/jwt-auth if you want something complex then sanctum can help you for example you can give token different abilities if you want to create an auth token use auth()->user()->createToken(); To create a token

You can use spatie roles and permissions. This package for jwt is good: https://github.com/tymondesigns/jwt-auth

tymon/jwt-auth: https://github.com/tymondesigns/jwt-auth tymon/jwt-auth document: https://jwt-auth.readthedocs.io/en/develop/

jwt-auth provides a simple means of authentication within Laravel using JSON Web Tokens. JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.

I'm just going through a round of upgrades when using the package "tymon/jwt-auth". It looks like it's in a painful spot right now, hasn't had an official release in a long time, people are using develop branch, but it's colliding with another package (lcobucci 3.4.x). Long story short: look at https://github.com/PHP-Open-Source-Saver/jwt-auth

Should I verify the Firebase ID token while authentication and then issue and use a JWT for subsequent requests? I will use the php-open-source-saver/jwt-auth package for handling JWT. I know JWTs are used in stateless applications but I guess when the API guard verifies the user it will also fetch user records from the database.

Yeah I switched from laravel 9* to 8.* and I am using https://github.com/PHP-Open-Source-Saver/jwt-auth instead

So lucky you! I am so stuck with tymon/jwt-auth and even changed to php-open-source-saver/jwt-auth and they haven't fully compatible with 8.1 yet :(

PHP-Open-Source-Saver / jwt-auth . This package has 52 github stars , at the time of writing and has its documented at readthedocks