Skip to content

Instantly share code, notes, and snippets.

@odan
Last active August 16, 2022 18:49
Show Gist options
  • Save odan/2885ccd0d2f3a3df41bf5c3d6e9b4999 to your computer and use it in GitHub Desktop.
Save odan/2885ccd0d2f3a3df41bf5c3d6e9b4999 to your computer and use it in GitHub Desktop.
@Webudvikler-TechCollege

@odan, thank you so much. It worked for me. And thank you for the article! It has been a really great help!

@samuelgfeller
Copy link

samuelgfeller commented Nov 18, 2020

Hello @odan

Thank you so much for this article. I have 2 questions the first isn't so important. I already decided that I will implement the way it's in your doc.

What are the pros / cons of using a library like tuupola/slim-jwt-auth versus an approach like in this article and what do you recommend in the end?

Do you know any projects where these JWT-Functions are being tested? Or do you have examples?

@odan
Copy link
Author

odan commented Nov 18, 2020

Hi @samuelgfeller My approach is more Middleware and Routing based while the tuupola/slim-jwt-auth approach uses an array to configure the different routes. For me the array based protection is not so good to maintain in the long run, for example when you add or change route paths you may miss some routes and suddenly it's unprotected. I prefer to explicitly add the JwtAuthMiddleware to specific routes or route groups in routes.php. You can open the routes.php file see what is protected. My approach also makes it easier to fetch users from the database (see TokenCreateAction) instead of loading it from a fixed array. I think you have to decide what's better for your specific use case.

@samuelgfeller
Copy link

@odan that's very pertinent! I think easily worth mentioning in the article. Below where you link to tuupola/slim-jwt-auth or somewhere near.

@odan
Copy link
Author

odan commented Nov 18, 2020

@samuelgfeller Yes, thanks. I will add it to the article.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment