Skip to main content
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
Source Link

JWT can either be signed, encrypted or both. Please use the case of encrypted and signed for secrecy of the App2 user-id (and other details) transmitted via JWT. Please refer thisthis for more details. It's recommended to sign and then encrypt but vice versa is also possible.

JWT can either be signed, encrypted or both. Please use the case of encrypted and signed for secrecy of the App2 user-id (and other details) transmitted via JWT. Please refer this for more details. It's recommended to sign and then encrypt but vice versa is also possible.

JWT can either be signed, encrypted or both. Please use the case of encrypted and signed for secrecy of the App2 user-id (and other details) transmitted via JWT. Please refer this for more details. It's recommended to sign and then encrypt but vice versa is also possible.

Source Link
Karan Bansal
  • 268
  • 1
  • 2
  • 8

JWT can either be signed, encrypted or both. Please use the case of encrypted and signed for secrecy of the App2 user-id (and other details) transmitted via JWT. Please refer this for more details. It's recommended to sign and then encrypt but vice versa is also possible.