Azure Digital Twin Sample Code Error : AADSTS50011

jefftblumenthal 1 Reputation point
2020-08-18T16:14:38.287+00:00

Hi,

I have been working with this sample code:
https://learn.microsoft.com/en-us/samples/azure-samples/digital-twins-samples/digital-twins-samples/

specifically with the AdtSampleApp project.

I have been following the instructions for this project from here: https://learn.microsoft.com/en-us/azure/digital-twins/tutorial-command-line-app

I have setup my ADT and the AD according to the instructions.

However, when I run the application, SampleClientApp in the project, it will authenticate ok, but when I get to line 58 of the Program.cs I get the following error:

------------------------

Request Id: cfc48259-361b-4a86-85f2-f098438f1500
Correlation Id: 1f319b0c-aeee-478c-9bdf-07915c29760c
Timestamp: 2020-08-18T16:10:30Z
Message: AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: '<clientId>'.

------------------------

Note, I replaced my clientId guid with the text <clientId>.

Can I please get some help on how to get passed this error?

Thank you for your help.

Azure Digital Twins
Azure Digital Twins
An Azure platform that is used to create digital representations of real-world things, places, business processes, and people.
224 questions
{count} votes

1 answer

Sort by: Most helpful
  1. QuantumCache 20,261 Reputation points
    2020-08-18T20:45:51.43+00:00

    Hello @jefftblumenthal , Thanks for the confirmation.

    Do you see any browser loaded for the authentication? when you run the sample code?

    Please refer to this Github issue: https://github.com/MicrosoftDocs/azure-docs/issues/60633#issuecomment-675250661

    Could you please try using the Azure.Identity v1.1.1 instead of the latest version "Azure.Identity v1.2.0" to get unblocked on this issue as a workaround! Please let us know if that works for you.

    18521-image.png

    Update: 08/26/2020 For InteractiveBrowser issue fix.

    We have now the NuGet package fixed in the latest Azure.Identity(1.2.2)

    So please make use of the latest NuGet Package Azure.Identity(1.2.2)

    Please let us know over here or comment on the Github Doc to get further help in this matter.