Check mapping configuration

This method checks if a mapping configuration exists for a specific triplet of parameters: serviceName, accountId and url. If it exists, am mTLS request can be used with the relevant certificate.

The aim of this method is to minimize sending TLS only requests through the service, since the mTLS service is throttle protected. This API allows the consuming service to know if mTLS is configured for the specified parameters.

Request

Query Parameters

• Versions only differ by the response type (see below).

Request Headers

Request Body

Contains list of CertificateMappingParamters objects:

[
   {"serviceName":"IDP","accountId":"52653865","url":"https://lp-idp-qa.dev.lprnd.net/mock/auth/token"},
   {"serviceName":"TEST_SERVICE","accountId":"52653865","url":"https://lp-mtls-qa.dev.lprnd.net/test"}
]

Note: You must enter a complete URL, including any URL parameters if they exist. For mapping purposes, the entire URL will be checked.

Note: You must enter a complete URL, including any URL parameters if they exist. For mapping purposes, the entire URL will be checked.

Response

Response Codes

Response Body

V1 response (default)

{
 "CertificateMappingParamters{serviceName='TEST_SERVICE', accountId='52653865', url='https://lp-mtls-qa.dev.lprnd.net/test'}": true,
 "CertificateMappingParamters{serviceName='IDP', accountId='52653865', url='https://lp-idp-qa.dev.lprnd.net/mock/auth/token'}": false
}

V2 response

• The "doExist" status is added to the submitted parameters.

[
    {
        "serviceName": "IDP",
        "accountId": "52653865",
        "url": "https://lp-mtls-qa.dev.lprnd.net/test",
        "doExist": true
    },
    {
        "serviceName": "TEST_SERVICE",
        "accountId": "52653865",
        "url": "https://lp-mtls-qa.dev.lprnd.net/test",
        "doExist": false
    }
]

Entity Structure:

CertificateMappingParameters object which contains: