JWT Authentication

JWT signature is used to verify that the token is signed by the sender and not altered in any way. The Signature is created using the Header and Payload segments, a signing algorithm, and a secret or public key.

To enable JWT authorization, set the ms.security.tokencheck.enabled parameter as Y.

Properties Description
JWT_TOKEN_ISSUER Identifies the issuer of the authentication token.
JWT_TOKEN_PUBLIC_KEY Indicates Base64 encoded public key content that can be directly loaded as a public key certificate.
JWT_TOKEN_PRINCIPAL_CLAIM Indicates the claim in which the user principal is provided.

ID_TOKEN_SIGNED 

Enables the JWT signature validation along with the header and payload.

You can configure JWT authorization for the following containers:

Docker

For Docker deployment, set the below mentioned JWT configuration properties as Environment Variables in API container of both ms-receipt.yml and ms-receipt-standalone.yml.

#--- JWT Configuration ---
ms.security.tokencheck.enabled: 'Y'
JWT_TOKEN_PRINCIPAL_CLAIM: "sub"
JWT_TOKEN_ISSUER: "ReceiptIssuer"
ID_TOKEN_SIGNED: "true"
JWT_TOKEN_PUBLIC_KEY: "LS0tLS1CRUdJTiBQVUJMSUMgS0VZLS0tLS0NCk1JSUJJakFOQmdrcWhraUc5dzBCQVFFRkFBT0NBUThBTUlJQkNnS0NBUUVBbnp5aXMxWmpmTkIwYkJnS0ZNU3YNCnZrVHR3bHZCc2FKcTdTNXdBK2t6ZVZPVnBWV3drV2RWaGE0czM4WE0vcGEveXI0N2F2Nyt6M1ZUbXZEUnlBSGMNCmFUOTJ3aFJFRnBMdjljajVsVGVKU2lieXIvTXJtL1l0akNaVldnYU9ZSWh3clh3S0xxUHIvMTFpbldzQWtmSXkNCnR2SFdUeFpZRWNYTGdBWEZ1VXVhUzN1RjlnRWlOUXd6R1RVMXYwRnFrcVRCcjRCOG5XM0hDTjQ3WFV1MHQ4WTANCmUrbGY0czRPeFFhd1dENzlKOS81ZDNSeTB2YlYzQW0xRnRHSmlKdk93UnNJZlZDaERwWVN0VGNIVENNcXR2V2INClY2TDExQldrcHpHWFNXNEh2NDNxYStHU1lPRDJRVTY4TWI1OW9TazJPQitCdE9McEpvZm1iR0VHZ3Ztd3lDSTkNCk13SURBUUFCDQotLS0tLUVORCBQVUJMSUMgS0VZLS0tLS0="

Bookmark Name Actions
Feedback
x