Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup Identity Framework - Docker B2C tenant creation Error Not Found Resource with ID #199

Closed
basztech opened this issue Sep 26, 2022 · 5 comments

Comments

@basztech
Copy link

Hi,

Following the quick start guide using Docker fails early in the script on setting up the identity framework. It looks like the script is trying to validate against the wrong path. Is there a work around or do I ned to forget using Docker?

Error message....

Waiting for 30 seconds for B2C tenant creation...
ERROR: (NotFound) Resource with ID '*********************01/saas-identity/bastechllc.onmicrosoft.com' does not exist.
Code: NotFound
Message: Resource with ID '*********************01/saas-identity/bastechllc.onmicrosoft.com' does not exist.
Target: resource

My Azure resource group that was created by the script...

{
    "id": "/subscriptions/*********************01/resourceGroups/saas-identity",
    "name": "saas-identity",
    "location": "eastus",
    "properties": {
        "provisioningState": "Succeeded"
    }
}
@landonpierce
Copy link
Collaborator

@basztech Thanks for reporting the issue. Can you confirm (through the portal) if the B2C tenant is actually getting created within that resource group?

@basztech
Copy link
Author

No resources have been created in that resource group.

@landonpierce
Copy link
Collaborator

Hmm, it looks like that tenant name has been taken. Does it exist maybe in another resource group or subscription? Or did you create it at one point and then delete it? B2C tenants are notoriously difficult to delete once they've been created :).

Can you try picking a different name to double check this theory? We're working on adding a check to the script to warn you beforehand, but in the meantime, you can check the name in the Azure portal first.

image

@basztech
Copy link
Author

basztech commented Sep 26, 2022

But I do own that tenant. Ah, looking at the Azure doco, it makes a bit more sense since we are creating an additional active directory and need an additional tenant, not the existing one.

I tried a new tenant name and it works just like you said, until...

Consent granted
Creating App Registration asdk-saas-app
Add-MgApplicationPassword_AddExpanded: /app/Saas.IdentityProvider/scripts/B2C-Create.ps1:628
Line |
 628 |        $newAppSecretObject = Add-MgApplicationPassword -ApplicationId  …
     |        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Resource '4f519cb4-0da0-497d-a8f8-1a9bc897c9d2' does not exist or one of its queried reference-property objects are not present.

A second run with the same parameters and not removing anything already created has gone past this stage, so all good for now.

Thanks for your help.

@basztech
Copy link
Author

So this was not an issue with the code but with my understanding of the implmentation.

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

No branches or pull requests

2 participants