jose-jwt VS jose

Use the jose-jwt library and thank me later

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.

JWT - jose

For demo purpose, we'll use some popular libs e.g. jose.

This module provides a lot of useful functions and utilities, but we will focus only on a couple of them. You can read more about the module itself if you feel like it.

Honestly, not exactly sure what the correct order is. The standard for encrypted jwt is called JWE. Most programming languages will have some kind of library that will handle the small details like order of operations. Example: jose for js.

I used standard Web APIs such as fetch() and WebCrypto. The most common thing I had to do was JWT token generation/validation. I worked with the jose library (the only dependency in the project) because it is cross-platform and also works with the WebCrypto API.

Biggest sharp edge I've encountered is the very much WIP WebCrypto API support. In practical terms, this means things like signing/verifying JWTs is not very well supported: https://github.com/panva/jose/discussions/243

That said, the situation is improving rapidly, and I've been personally willing to bet that the support will be solid by the time I finish prototyping and need to start adding auth to my latest project.