Dicom Service Access issue via postman

telemedica 0

We have deployed dicom service also we have done app registration, after we got the clientID,tenantID,client secrets and dicom service URL.When we generate bearer token by Azure cli we can able to access the dicom service.

When we try to get the bearer token using postman with the client ID,tenant ID,client secrets and dicom service URL we got the bearer token but not able to access the dicom service, instead it show 401 authentication issue.

MuthuKumaranMurugaachari-MSFT 22,151 Reputation points

2023-07-28T13:37:46.6033333+00:00

telemedica Thanks for posting your question in Microsoft Q&A. When you generate an access token using Postman, can you validate if you follow the steps described in Get Azure AD access token? Also, make sure the audience parameter is mapped correctly. The doc has steps to decode the access token via https://jwt.ms and this will help in examining the claim.

If you still face the issue, share the timestamp, activity/request/correlation ID and full error message/response info. That will help in troubleshooting the issue.
telemedica 0 Reputation points

2023-07-31T11:40:24.5266667+00:00

Hello,

Thank you for your reply, actually we are trying to get the token for dicom service, but the link which you provided to us is redirecting to FHIR access token page.
MuthuKumaranMurugaachari-MSFT 22,151 Reputation points

2023-07-31T14:02:11.1566667+00:00

telemedica Sorry for the confusion. To clarify, the steps to troubleshoot for DICOM is also similar and checkout the discussion 401 error while accessing DICOM API and reference doc Get Access Token Using Postman specifically for DICOM.

Any additional details such as timestamp, activity/request/correlation ID and full error message/response info would help in reviewing the logs.