Integration endpoint returning "ASID is not configured in the application" error

e-Referral Service (e-RS) e-Referral Service FHIR API
41

I’ve put that request in - is the screenshot above from a UUID that we’ve previously updated? Do you have the ID#

42

Hi @tony.marsh1 The smart card ID used to book those eRS referrals was: 555295320104

43

Thanks @tony.marsh1 , our A005 call is now successful!!

When we make the follow-up A042 call to retrieve the document, we get an error back, details below

GET: https://int.api.service.nhs.uk/referrals/FHIR/R4/Binary/3a410236-bfa1-4474-9bb1-08d5f6ac68bf

Authorization: Bearer REDACTED
Accept: application/fhir+json
X-Correlation-ID: 68763192-93a0-40c7-9b73-beaa8f8e4ad2_2

Response:

<Error>
    <Code>InvalidArgument</Code>
    <Message>Only one auth mechanism allowed; only the X-Amz-Algorithm query parameter, Signature query string parameter or the Authorization header should be specified</Message>
    <ArgumentName>Authorization</ArgumentName>
    <ArgumentValue>Bearer vfcLw2K9wXzhGitDTHJRgZua27AV</ArgumentValue>
    <RequestId>87E7J5CHR554M1HK</RequestId>
    <HostId>vqLr3Vc9cc3yn+PgkR1QJ+xymeRH0B4wSYFlVxPIYg91pBbjsOWcs936d0y/NEVXaJlcVpIxjFo=</HostId>
</Error>
44

Might need some help with that one. But seems to indicate you’re using two auth methods at once and getting an error. eg, signed JWT and CIS auth header?

45

Hi @tony.marsh1 It looks like it’s related to this issue. Leave this with us and we’ll see if we can work through it

Rinaldo

46

@tony.marsh1 by not following the redirect on the A042 call and making a fresh call to AWS without the NHS access token, A042 now successfully returns the documents.

Thanks for your help.

47

no problem, good luck with your development - and thanks for using the forum so others can see similar issues/answers