jwt VS go-guardian

To add JWT authentication to our ToDo application, we'll be using the Golang-jwt library. The golang-jwt package simplifies the implementation of JWTs in Go applications, offering a suite of convenient functions that abstract away the complexities associated with token creation, verification, and management.

golang-jwt/jwt - GitHub

To create a secure Role-based authentication scheme, we need to generate a unique token when the user authenticates. This is then used to track their assigned role as they consume the availed resources. In this project we are going to use the jwt-go package to generate a JWT token that will encapsulate the user details, assigned role and permissions.

Yes. Currently maintained version is here: https://github.com/golang-jwt/jwt

Libraries used bcrypt: https://pkg.go.dev/golang.org/x/crypto/bcrypt golang-jwt: https://github.com/golang-jwt/jwt Gin (Http framework): https://github.com/gin-gonic/gin

We will implement Golang JWT authentication using a go-jwt package.

Authorization jwt

At least template-wise, I've developed pongo2 mimicking Django's template engine which I use myself for various projects. For the rest I usually stick with the standard library (net/http), golang-jwt, the Gorilla toolkit (note that it's been archived recently) and some software architecture patterns for middlewares, database abstraction, etc.

Either way, you will need to validate the signature of the JWT. You can do this with the public key and a library such as https://github.com/golang-jwt/jwt.

go-gurdian

https://github.com/labstack/echo This is going to be my next project I look at. Alternatively you can incorporate the security bits manually by importing something like: https://github.com/shaj13/go-guardian