jose | JSON Object Signing and Encryption Framework | Authentication library

The answer is to use String for (de)serialization for those facing this problem. Why, you ask? According to the RFC, JWK is a string in the JSON format. While nimbusds:nimbus-jose-jwt defines a JWK object, any APIs that return valid JWK (or JWKSet) can assume that it's a string.

I also raised this issue with the developers of this package, and they recommended using String or Map for (de)serialization.

You are trying to group from a column that you aren't querying.

Try including this fields on the query

You need your keys in a format that Node.js recognizes. KeyObject create*Key APIs recognize and the key is supported in - for Ed25519 keys that is, assuming Node.js >= 16.0.0:

• PEM/DER in SPKI for public keys
• PEM/DER in PKCS8 for private keys
• JWK for both public and private keys

Here's a snippet that uses DER.

Reason of the issue

It is expected browserslist to return an entry for each version ("safari 15.2", "safari 15.3") instead of a range ("safari 15.2-15.3"). So, this is just a bug in the parsing logic of Safari browser versions which needs to be corrected and will be done soon in fixed versions of Angular 12/Angular 13. Link to details is here.

IMPORTANT UPDATE:

This is fixed in v12.2.16 and v13.2.1, please update if you are experiencing this issue. Users on v11 shouldn't be affected. Link to details is here. If you can not/do not want to update for any reason, then one of the workarounds below can be used.

Workarounds:

Modify .browserslistrc

Add to .browserslistrc such lines:

In order to interact with an ERC20 token, you have to create an instance of it from the desired contract. You would need to import ERC20 to your nfts contracts, and then create an ERC20 token instance pointing to your token. It would be something like this:

Try moving jws.setPayload(payload); down to after the jws.setCompactSerialization(...); line.
I think that jws.setCompactSerialization(...); is overwriting the payload to be the empty string, which would break the signature verification.

Add the @ sign to position to get it to render in the page:

Change this:

If I understood you correctly, then perhaps this example below can help you:

You have three problems with your code.

1. due to the asynchronous nature of the promises, key gets a value when the promise is fulfilled (in the .then part), but that happens after the next line gets called.

   Place a console.log(key) directly after the line jose.JWK.asKey(... and you see you get "undefined" as a result. So there is actually no key.

2. the k value in a JWK is treated as a Base64Url encoded octet. When you sign the token, you have to use the base64url decoded value of k, but not k directly.

3. the secret "SuperSecretKey" is too short for node.jose. For the HS256 algorithm, the secret has to be 256 bits long. node.jose seems to be quite strict, compared to other libs.

To solve the first problem, you can either nest the calls (which quickly becomes hard to read, or use the async/await syntax like shown below: