question

Sab-1606 avatar image
0 Votes"
Sab-1606 asked Danstan-MSFT answered

Requested Authority Not Found

I'm following this tutorial for issuing Verifiable Credentials through Azure AD. I've replaced the sample app appsettings.json file with the specified property values. However when scanning the QR code, the Microsoft Authenticator app returns an error with the code authorityNotFound and the message "Requested authority could not be found".

I am assuming this is to do with the IssuerAuthority property in appsettings.json. This value is my DID copied directly from the Azure Verifiable Credentials (Preview). The same value is provided for the VerifierAuthority property as well, as stated by the tutorial.

Does anyone have any ideas how to fix this?





azure-ad-verifiable-credentials
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

Danstan-MSFT avatar image
0 Votes"
Danstan-MSFT answered

This could mean your authority and tenant specify different regions. Quoting from the docs docs

Applications that use the Azure Active Directory Verifiable Credentials service must use the Request API endpoint that corresponds to their Azure AD tenant's region.

To confirm which endpoint you should use, we recommend checking your Azure AD tenant's region as described above. If the Azure AD tenant is in the EU, you should use the Europe endpoint.






5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.