jwt VS jose-jwt

There is a special type NumericDate (https://github.com/cristalhq/jwt/blob/main/numeric_date.go) to handle this, however if you have an example where it doesn't work with golang-jwt/jwt please share it, will be happy to add a test for this (or even a fix if something is wrong :( )

Authentication is one of the most important part of almost every web application. We must ensure that every user can create, read, update and delete only data for which it's authorized. For that purpose we will use JWT (JSON Web Token). Fortunately, there are various Golang modules specialized for this. One that will be used in this guide can be found in this GitHub repo. Current latest version is v3 which can ne installed by running go get github.com/cristalhq/jwt/v3.

As far as using something other than oAuth its all about what your app supports. If basic authentication is supported, go ahead and send your credentials straight to the server as a -credential and skip ADFS. The REST API we have at work can handle tokens signed with different keys so if a client wanted to generate a RSA keypair and share the public key with us they could generate and sign their own token (jose-jwt works well in PS for this) and submit it straight to the server without going through ADFS. Again, its all about what your app is capable of.