Authentication Issue: Unable to Fetch FHIR Resources After Deploying DICOM Cast and Syncing Metadata into FHIR Server for Azure
NancyOsalaniya opened this issue · 7 comments
I've deployed DICOM Cast successfully. And I have performed all the steps of Sync Medical Imaging Server for DICOM metadata into FHIR Server for Azure.
I am unable to fetch FHIR resources when I setup authentication in the FHIR service.
As you can see in the below diagram, If I skipped step no 3 then I'm able to fetch FHIR resources.
I cannot fetch FHIR resources when I set up authentication in the FHIR service. It is working fine when I skip that step. Do you have any ideas on why I'm unable to get FHIR resources?
@NancyOsalaniya what type of FHIR service are you using? Are you using any network isolation?
@KnicKnic I'm using Azure Health Data Services' FHIR service.
I cannot fetch FHIR resources when I set up authentication in the FHIR service. It is working fine when I skip that step. Do you have any ideas on why I'm unable to get FHIR resources?
@NancyOsalaniya sorry can you explain this a little more?
Azure Health Data Services: FHIR uses Azure RBAC and always has authentication enabled. If you're setting up an application to access FHIR against the managed service were the correct roles also assigned? https://learn.microsoft.com/en-us/azure/healthcare-apis/authentication-authorization#application-roles
Hi @brendankowitz , sorry for the delay in the reply.
Yes, the roles have been assigned properly as mentioned in the document.
But I was asking is that, whenever I set up this Authentication step in the FHIR Service at that time I'm not able to get FHIR resources. But if I skip this step, then it is working. But I think that this is step is mandatory one. In that case, could you please look into the matter why I'm not able to fetch FHIR resources while I configure this Authentication step?
@NancyOsalaniya - From the work flow it seems you are updating the FHIR service audience URL with client App ID URL. Approach you can try - instead of updating the FHIR service audience URL, register a client application and provide it access to FHIR service. Let us know if this approach resolves the issue for you.
@NancyOsalaniya - Issue will be closed in a week, incase of no further updates.
Closing the issue with above comment