Authentication using MS - JWT

This section helps you enable the authentication for Docker, Azure, AWS, and K8 by using MS - JWT.

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 authorisation, you should set ms.security.tokencheck.enabled to Y in ENV.env file. The table below describes the JWT authentication properties.

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.

NOTE: JWT Authorization is by default disabled in Azure/AWS/K8 stack.

Enabling Authentication for Docker

Set the following JWT configuration properties as Environment Variables in the API container of ms-duediligence-mongo.yml / ms-duediligence-postgresql.yml which in turn will refer the ENV.env file for the value of the respective JWT configuration properties.

Enabling Authentication for Azure

For Azure deployment, set the following mentioned JWT configuration properties in both install.sh/install-postgresql.sh and install.bat/install-postgresql.bat.

Enabling Authentication for AWS

In AWS deployment, set the following mentioned JWT configuration properties in install-aws.sh and install-aws-postgresql.sh.

Enabling Authentication for K8

For K8, navigate to \duediligence\ms-duediligence-package\ms-duediligence-package-docker\src\docker\k8\on-premise\svc\templates\svc\ and configure the following JWT configurations in duediligence-configmap.yaml.

Copyright © 2020- Temenos Headquarters SA

Published on :
Monday, May 2, 2022 5:52:48 PM IST

Feedback
x