In a scenario where you want other sites to validate your sites JWT token but you dont want them to generate new token on your behalf. This will be helpful

In JWT singing is done with private key only. This process occurs at server end so your private key remains secure. If the client wants to verify the token the server can expose the public key so the client side can also verify the token.

@@TechnoSaviour Under RSA encryption, messages are encrypted with a code called a public key, which can be shared openly. Due to some distinct mathematical properties of the RSA algorithm, once a message has been encrypted with the public key, it can only be decrypted by another key, known as the private key. Each RSA user has a key pair consisting of their public and private keys. As the name suggests, the private key must be kept secret.

THIS is what many blogs say about RSA

@@harshmittal3072 Signing is different from Encryption, although both use a key-pair generated by RSA. Both differ in the objective: Assume Alice uses her key-pair for the examples Encryption - The objective is to protect the data. Let's say Bob 'encrypts' a message using Alice's public key. This allows only Alice to read the data (using her private key), but there's no way to verify that it was indeed Bob who encrypted the data, or the source of the data, since anyone can use Alice's public key. Signing - The objective is to verify the source of the data. Let's say Alice 'signs' a message using her own private key. This allows anyone to verify that this data was indeed from Alice (using her public key), but there's no way to protect the data, since, again, anyone can use Alice's public key. Hope this explanation helps. You can read more about this at www.encryptionconsulting.com/education-center/encryption-and-signing#:~:text=Encryption%20uses%20a%20key%20to,of%20encryption%20in%20its%20process

You have to specify the algorithm

Same for me

@@jpbl2418 I realized later that my public and private key did not match. No idea why. Had to regenerate.