JWT Authentication MSF

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.

JWT Authorization, is enabled by default in the ODMS - to disable this functionality, the setting ms.security.tokencheck.enabled should be set as N.

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-storage.yml.

#--- JWT Configuration ---
ms.security.tokencheck.enabled: 'Y'
JWT_TOKEN_PRINCIPAL_CLAIM: "sub"
JWT_TOKEN_ISSUER: "Fabric"
ID_TOKEN_SIGNED: "true"
JWT_TOKEN_PUBLIC_KEY: "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnzyis1ZjfNB0bBgKFMSvvkTtwlvBsaJq7S5wA+kzeVOVpVWwkWdVha4s38XM/pa/yr47av7+z3VTmvDRyAHcaT92whREFpLv9cj5lTeJSibyr/Mrm/YtjCZVWgaOYIhwrXwKLqPr/11inWsAkfIytvHWTxZYEcXLgAXFuUuaS3uF9gEiNQwzGTU1v0FqkqTBr4B8nW3HCN47XUu0t8Y0e+lf4s4OxQawWD79J9/5d3Ry0vbV3Am1FtGJiJvOwRsIfVChDpYStTcHTCMqtvWbV6L11BWkpzGXSW4Hv43qa+GSYOD2QU68Mb59oSk2OB+BtOLpJofmbGEGgvmwyCI9MwIDAQAB"