Microservices
Updated On 03 September 2024 | Min(s) read

Enabling Authentication using JWT-MSF

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

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.

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

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.

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

Enabling Authentication for K8

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

Copyright © 2020- Temenos Headquarters SA

Published on :
Tuesday, September 2, 2025 12:38:44 PM IST