Synthetic tests fail, when using API Key credentials from the 'Current Instance' location, due to an incorrect Authorization header - Known Error

Synthetic tests fail, when using API Key credentials from the 'Current Instance' location, due to an incorrect Authorization header Description Synthetic Monitoring checks are using the wrong header for 'API Key' type credentials, when making the request directly from the Instance.

The header "Authentication" is used for the Bearer token from the API Key credential, when the correct header is "Authorization".

This does not affect MID Server or ACC locations, which use different code to put the request headers together.

Steps to Reproduce

Using Synthetic Monitoring app v1.3.1:

Create an API Key type credential record, containing the bearer token/key. From Service Operation Workspace, Synthetic Monitoring forms, create a synthetic test for an endpoint that requires a bearer token, using that API Key credential Add the "Current Instance" location Run the check, which can be done on demand using the sn_sow_synthetics_check_single_api_sysauto_script record for it. Actual behaviour:

The sn_sow_synthetics_check_single_api_result table will show the request failed with a with 4xx status authentication error. The sys_outbound_http_log table will confirm "Authentication=Bearer ..." is used in the header, when it needs to be "Authorization=Bearer ..."

Change the location to a MID Server or ACC one, and it will authenticate.

Expected behaviour:

Authentication with API Key credentials should work the same regardless of the Location.

Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.

The workaround is to change the Location, to make the requests to the endpoint via a MID Server or Agent Client Collector agent.