Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Support for Recent Changes to Azure AD - Verified Domains #151

Open
seversen opened this issue Nov 20, 2021 · 8 comments
Open

Support for Recent Changes to Azure AD - Verified Domains #151

seversen opened this issue Nov 20, 2021 · 8 comments

Comments

@seversen
Copy link

Describe the bug
New deployments of the Azure API for FHIR no longer complete successfully because there are resources/apps that use *.azurehealthcareapis.com and this is no longer valid per: https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-breaking-changes#appid-uri-in-single-tenant-applications-will-require-use-of-default-scheme-or-verified-domains

To Reproduce
Steps to reproduce the behavior, including exact commands you are running:

  1. Follow normal environment setup steps.
  2. Run .\Create-FhirServerSamplesEnvironment.ps1 -EnvironmentName -UsePaaS $true
  3. See error

Expected behavior
The entire sample environment should be provisioned. It only provisions the Key Vault and then throws an error similar to this:

Error occurred while executing NewApplication Code: Request_BadRequest Message: Values of identifierUris property must use a verified domain of the organization or its subdomain: 'https://example123.azurehealthcareapis.com' Details: PropertyName - identifierUris, PropertyErrorCode - HostNameNotOnVerifiedDomain, HostName - https://example123.azurehealthcareapis.com HttpStatusCode: BadRequest HttpStatusDescription: Bad Request HttpResponseStatus: Completed

This issue was also reported in a different GitHub project: https://github.com/Azure/azure-docs-powershell-azuread/issues/724

Are there any plans to address this? As far as I can tell, this project no longer works at all because of the new restrictions.

@seversen seversen changed the title Support for Recent Changes to Azure AD - Verfied Domains Support for Recent Changes to Azure AD - Verified Domains Nov 20, 2021
@acleith
Copy link

acleith commented Nov 30, 2021

I have also encountered this problem, as described above, same steps (with environment name specified via -EnvironmentName parameter)

@pogorman
Copy link

Same... any plans to remedy this?

@adm-kduddu
Copy link

Same , Any update on this please

@brian1985
Copy link

brian1985 commented May 11, 2022

I got it to move past this error.

There are two lines you need to update.
In Create-FhirServerSamplesEnvironment.ps1 and Create-FhirServerSamplesAuthConfig.ps1 change the text that mentions 'azurehealthcareapis' (appears once in each file) to 'yourdomain.onmicrosoft'

Example
$fhirServiceUrl = "https://${EnvironmentName}.azurehealthcareapis.com"
should change to
$fhirServiceUrl = "https://${EnvironmentName}.'yourdomain'.onmicrosoft.com"

where 'yourdomain' is the name of your AD domain (can be found by going to Azure Active Directory '(https://docs.microsoft.com/en-us/partner-center/find-ids-and-domain-names)

For now, it is installing and has gotten to the part where it says "User found, will update". I'll add more comments if it fails after that point and I can figure out any solutions.

@brian1985
Copy link

After waiting a few minutes for the steps to complete I still get one error after
Warming up site...
Invoke-Webrequest : The remote name could not be resolved: 'xxxxxxxx'

So I don't know if my solution didn't work and just hid an underlying problem or what.

@adm-kduddu
Copy link

adm-kduddu commented May 11, 2022 via email

@brian1985
Copy link

I'm not sure I can help much more then that. I very new with azure and kindof stumbled upon my solution. And I am stuck on the next step, so I'm not sure it worked right.

Honestly, since I am still having problems, I might try seeing if I can do this using the build in Azure API for FHIR resource

@aidanplunkitt
Copy link

Hi all, give this a try and let me know if it works for you.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants