jwt-go VS Goyave

My only suggestion, because I haven't seen anyone else mention it, is researching your dependencies. In the app you're using https://github.com/dgrijalva/jwt-go, which isn't maintained anymore and in their repo they state that you should use https://github.com/golang-jwt/jwt instead.

There are so many tools created tools using golang like the gh-cli, cockrach-db, jwt, etc. You can see a whole list of applications/tools/frameworks written in Go from this awesome list

If it is using "github.com/golang-jwt/jwt" under the hood than all you have to do is override the Valid() method on your claims object.

The code logic is query user record from database by input parameter username, if not found, return Incorrect username or password error, if password was correct, issue token. The jwt library used here is golang-jwt/jwt

Abandon https://github.com/dgrijalva/jwt-go library due security issues. Now I use https://github.com/golang-jwt/jwt#jwt-go

Use jwt (jwt.io, https://github.com/golang-jwt/jwt) shoveling the params into a MapClaims.

Go JWT Implementation Link

The boilerplate application uses the dgrijalva / jwt-go library to work with JWTs. Besides the standard set of claims fields, this library allows you to describe additional fields. In the application, this makes it possible to write to the token the ID of the user to whom it was issued. The library supports the NewWithClaims () and Parse () functions used in the AuthHandler application to create and validate tokens. Also, the Echo framework has a JWT middleware that uses the specified library to validate tokens. This middleware is hooked up in the ConfigureRoutes () function of the template application that declares the routing.

There might be many different packages, but I think this one is the most popular: https://github.com/dgrijalva/jwt-go. So let’s copy its URL, and run go get in the terminal to install the package:

Take a look at Goyave, it is inspired by Laravel on some aspects. It's focused on REST APIs only. I wouldn't say it's "the best" because there is no best, it always depends on your needs. Anyway, yesterday I released the first preview version of the v5, a rewrite of the framework trying to solve many weak points of the previous version. It's poorly documented for now because it is still WIP and I wouldn't recommend building production applications with it. Stick to v4 for this for now.

I can't say it rivals because it's still far from that, but I'm working on Goyave. The goal is to make a complete package so you can focus on your business logic as much as possible. It's focused on REST APIs only.

You can try https://goyave.dev/ ?

Take a look at Goyave.

Check out Goyave and see if it would fit your needs.

Goyave is not widespread but it's inspired by Laravel on some aspects. Try it out!

Hey! That's the goal of Goyave, a framework I'm working on. Its creating was motivated by the same complaint you have.

I'm using Goyave, removes the hassle of setting up a lot of things yourself for bigger projects or APIs that are going to be exposed to the internet. Otherwise for internal services it's probably overkill.

Take a look at Goyave.