MTOA Wrapper

Owned by Alex Remo
Last updated: Aug 22, 2023
1 min read

Configuring API key and JWT Token for a new LOB

General

To communicate properly with MTA API through MTOA Wrapper it is required to send API Key and JWT token as part of any request. The article explains how to configure a Azure KeyVault to have the corresponding keys related to a specific LOB

Sending a message to MTOA Wrapper

In order to make a successful request to MTA API through MTOA Wrapper, special header should be sent along with service bus message:

Header name: WLM_LOB_ID

Header value: LOB Id

MTOA Wrapper processing

When the Service Bus message is received by the Wrapper, it will be looking for a header with name "WLM_LOB_ID"

The LOB Id will be used to create a secret name that should be pre-existing inside corresponding Azure KeyVault.

There are two secrets used for MTA API authentication/authorization:

API Key

JWT Token

Each of the secrets have a pre-defined corresponding secret name per LOB:

[LOB ID]-MTAAPIKEY

[LOB ID]-MTAJWTTOKEN

The Wrapper will use the secrets' values for subsequent call to MTA API. In such way only a specific LOB data will be returned or processed inside MTA API.

To send a successful request to MTA API through MTOA Wrapper

  1. Add “WLM_LOB_ID“ header with LOB ID as value. Example: “001”

  2. Define 2 secrets inside corresponding Azure KeyVault. Example: For LOB ID = 001 you should define 001-MTAAPIKEY and 001-MTAJWTTOKEN