Enabling Authentication using JWT

This section helps you to enable the authentication for J2EE using JWT.

Marketing Catalog Microservice supports four stacks. They are Azure, AWS, and J2EE. AWS and Azure are authenticated by default whereas you need to enable authentication for J2EE.

To enable authentication for J2EE, you must configure and deploy the respective WAR files.

• Configuration
• Deployment

Configuration

Before deploying the WAR file, you must configure the WAR file of the required stack. To do so, you must perform the following tasks:

Prerequisites

Ensure that you meet the following prerequisites:

• If you want to enable authentication for the J2EE stack, you must download the j2ee-iris WAR file named ms-marketingcatalog-j2ee-iris-DEV.0.0-SNAPSHOT.war and the J2EE package for must be up and running.

Generating JWT Token

JWT Token is usually generated and supplied by the other system which is consuming the endpoints published in the war. The public key in base 64 encoded format has to be configured in the war prior to the deployment.

You can generate JWT token using JWT site. A sample token generation is given below.

A sample screenshot (Debugger) from JWT site is given below.

Configuring JWT

This section helps you to configure JWT.

Procedure:

1. Uncomment the following in Web.xml.
   Classpath

   classpath:spring-jwt-iris-authenticator.xml

   Filter

   <filter>
   <filter-name>springSecurityFilterChain</filter-name>
   <filter-class>org.springframework.web.filter.DelegatingFilterProxy</filter-class>
   </filter>     
   <filter-mapping>
   <filter-name>springSecurityFilterChain</filter-name>
   <url-pattern>/*</url-pattern>
   </filter-mapping>

2. Comment the NullBean and Uncomment T24SpringSecurityContextFilter as shown below in applicationContext.xml .
   Security Filter

   <!-- <bean id="t24SecurityFilter" class="com.temenos.irf.comms.security.defaultimpl.NullBean" /> -->
   <bean id="t24SecurityFilter" class="com.temenos.irf.security.t24.T24SpringSecurityContextFilter" />
   

3. Set the claims that required to be extracted from the jwt payload and token validation parameters in spring-jwt-iris-authenticator.xml.
   1. Set the value of principalClaim as sub, issuer from JWT Token payload (Fabric), and public key in base 64 format in pkEncoded.
      Token Validation Parameters

      <beans:bean id="oidcProviderServer" class="com.temenos.security.oidc.common.OidcProviderServer">
          <beans:property name="issuer" value="Fabric" />
          <beans:property name="pkEncoded" value="TUlJQklqQU5CZ2txaGtpRzl3MEJBUUVGQUFPQ0FROEFNSUlCQ2dLQ0FRRUF2SjJoQ3pxZXMwUUxkbVJUcFVnSA0KZW9LR1l3QWN5ejZYcTF6cWVBMjdMZWQxbXF5dzZETnJ5enl0bWtCNGNEdUc0cldvQXRydVZiY3ZmUDhVdi9nbg0KVXdDQXg2dzhxb2E4czNqa0ljUFM3QWlwNEFXTkNJNTdaRk9KSU1aNmx3SHRhWEgxaEIvUElnYk54NjlIb3VkSw0KSUc2WDZRdlZlOUtYbWhlbytVbGZsakE1Mm4zWmY5QnlRKy9xQ2w3eXJwcENQYk5PUHFraHBNQ0ZtQ0VrMjQxTg0KWDdxRlZKZTg0M1YzbnJwcXdJejROaVh5cjc0bFVaYVRGNUs0VHNZdnUreDBWemthRnpWUWlpUEw5QmVCZGZDMw0KYlA4cGJZMFd6MFFGQk1DRUJQRERzWWdEczZXcXBWam5CcklWTmVJdGZWY2hjK2JwZFNnWVVZRUR3RGlVczdpQg0KOFFJREFRQUI=" />
          <beans:property name="pkCertEncoded" value="" />
          <beans:property name="pkCertFilePath" value="" />
          <beans:property name="pkJwksUri" value="" />
          <beans:property name="decryptingJwkEncoded" value="" />
          <beans:property name="principalClaim" value="sub" />
      </beans:bean>

   2. Set the list of claims to be extracted from JWT as shown below.
      Claims

      <beans:bean id="requiredFields" class="com.temenos.irf.web.security.jwt.parser.RequiredFieldsExtractor">
          <beans:property name="claimsToExtract">
              <beans:list>
                  <beans:value>userId</beans:value>
                  <beans:value>roleId</beans:value>
                  <beans:value>dbx_user_id</beans:value>
                  <beans:value>registeredCompanyName</beans:value>
                  <beans:value>customerId</beans:value>
                  <beans:value>jti</beans:value>
                  <beans:value>client_id</beans:value>                       
               </beans:list>
          </beans:property>
      </beans:bean>

Deployment

After configuring the WAR file, you must deploy the configured WAR file on the J2EE Complaint Application Server. This section explains you about how to deploy the configured WAR file for the following stacks:

• J2EE

J2EE

Before deploying the authenticated WAR of J2EE, you must set up the following:

• Application Server
• MongoDB

Procedure:

1. Marketing Catalog j2ee iris war is generated under the target folder of the container project.

   

2. Perform the JWT token configuration in the generated war.
3. Deploy the generated war under the JBoss deployments folder.
   • For JBOSS, copy the artefact to the jboss/standalone/deployments folder.
   • For WebLogic, navigate to http://localhost:9001/console based on the URL configured while installing the server, and using the Install button, deploy the artefact.

   

4. Once the Marketing Catalog Microservice is up and running in application server, check the API's in the package with a JWT token.