xrpl.js VS node-jsonwebtoken

xrpl.js

JavaScript is one of the most widely-used programming languages, and as such has a massive community of active developers. Maintaining a JavaScript SDK enables these developers to seamlessly interact with the XRP Ledger, both in the browser and in Node.js. In addition, the JavaScript libraries (xrpl.js, ripple-binary-codec, ripple-keypairs, and ripple-address-codec) power many apps in the XRPL ecosystem, as well as packages from companies such as BitGo and Ledger.

JsonWebToken

The code uses the jsonwebtoken library to generate and verify JSON Web Tokens. It provides two endpoints, /login and /profile.

Well, I found how an OpenID Connect id_token should be validated. It wasn't straightforward in my case: I had to do a lot of research to validate my id_token. Let's see how to make this easy using Node.js and the jsonwebtoken npm package made by Auth0.

tests/test/__tests__: Writing tests is an important practice in software development, and in NPM packages you'll often see them stored in one of these folders. It can also be used to hold testing helpers and utility functions. Example from express.

As we could see, we go through the same procedure for every provider. First, we obtain access_token and use it to receive the user's info. In Increaser, once the user is validated, the back-end generates auth data via jsonwebtoken library.

I'm currently looking for a way to sign and refresh my tokens. Most tutorials out there make use of jsonwebtoken another library that hasn't been updated in more than 2 years (except a commit to readme).

I'm trying to integrate microsoft sign in into my app. I've got a backend endpoint that handles the auth redirect and exchanges the auth code for an ID Token and an Access Token. I've heard that some OIDC implementations don't require validating an ID Token. Does my set up sound like it should be doing this? If so, how do I validate these tokens? I'm planning on using this library https://github.com/auth0/node-jsonwebtoken which allows you to do jwt.verify(token, 'secret') but I can't figure out what 'secret' to use. Is this my client secret? Or something else?

Some verify functions such as the popular Auth0 node-jsonwebtoken library requires the public key in PEM format. There are many libraries available to do this conversation.

Don't write your own decode or verify functions, use a library like https://github.com/auth0/node-jsonwebtoken.

JWT