Enabling Authentication using MS - JWT

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

JWT Authorisation for Due Diligence microservices with the release version 202010 happens in the microservice layer using the environment variable configuration. The validation happens in-house and reduces any HTTP hop between IRF and Microservices.

JWT signature allows 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. 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.

Enabling Authentication for Docker

Set the following JWT configuration properties as Environment Variables in API container of ms-duediligence.yml.

Enabling Authentication for J2EE

In all the J2EE WAR deployment, navigate to the path \ms-duediligence-package-j2ee.ear\xxxx.war\WEB-INF\classes\properties\ and make the following JWT configurations in api.properties.

Enabling Authentication for Azure

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

Enabling Authentication for AWS

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

NOTE: JWT Authorisation is by default disabled in both Azure and AWS stack.

Bookmark Name Actions
Feedback
x