poadhika
commented
1 year ago It looks like you are trying to add the secrets to the keyvault but having trouble assigning the proper role that would allow you to add secrets to keyvault.
The above instruction is simply suggesting to add the servicepriciple that will be used to access that keyvault. If you are doing it manually and are logged in as yourself, then you should add your servicepriciple. But if this is automated process and you have created an app via appregistration in AAS which should be accessing the keyvault then add the appid of this app. Regardless of whatever serviceprinciple youa re using, that servicepriciple should have keyvault contributor access.
Overall the goal is allow to add all these properties to the keyvault.
HitakshiDobariya99
I've deployed DICOM Cast successfully. And performed all the steps of Sync Medical Imaging Server for DICOM metadata into FHIR Server for Azure. But unable to get the corresponding FHIR resources in FHIR service.
I've confusion in some steps of this doc.
1. While Setting the Authentication for your FHIR & DICOM App Services, I'm unable to set Audience, Authority, and Security: Enabled in DICOM service, and unable to set Security: Enabled in FHIR service.
2. While Updating Key Vault for DICOM Cast, In a document you've mentioned "Search for your Service Principle". Under the select principal, Which principle should I select? User Principle or Enterprise Application Principle? If Enterprise Application Principle then which application should I select?
Right now, I've not authenticated the DICOM service, and In the service principle, I've selected the user principle.
Here is the detailed container log: