401 Access Denied on call to A0042

[Petko_Petkov]

@Gary_England

When testing A042 in INT environment, we are receiving 401 status. The request to A0042 was preceeded by successful calls to A007 and A005 end points

URL: https://int.api.service.nhs.uk/referrals/FHIR/R4/Binary/f185d16b-7dd5-4a50-97d9-62494080a786

Headers:

Authorization: 0vGSeeV2cHrsB6C1L4PCyl0Ce46Q
NHSD-End-User-Organisation-ODS: RB8
NHSD-eRS-Business-Function: SERVICE_PROVIDER_CLINICIAN
NHSD-eRS-On-Behalf-Of-User-ID:
X-Correlation-ID: 17183684-D9A9-11F0-9A21-005056B4EE83
Accept: /

INT App ID for endpoint: ff20dedf-6bef-4b83-8455-4cd3bfe5f01a

The header values defined in A0042 specification are the same as for the STU3 A006 endpoint

Is this possibly because we need to request access to the A0042 endpoint for our application in INT, that is, A0042 has not been automatically made available for existing applications using A006?

Requests were sent at 11:14 on 15th December

Hi Gary,
Looking at the headers you’ve provided, it doesn’t look like the request is using an OAuth2 access token in the expected format. For A042 the Authorization header needs to be sent as:

Authorization: Bearer <access_token>

At the moment it looks like you’re sending a raw token value without the Bearer prefix, which would result in a 401. Could you please confirm you are generating a valid access token via the signed JWT flow and then passing it in the format above when calling A042.

Thanks,
Petko