This article portrays an issue where you get the mistake message “How to Fix AADSTS50011 – The answer URL <reply URL sent> determined in the solicitation doesn’t match the answer URLs arranged for the application <GUID>. Ensure the answer URL sent in the solicitation matches one added to your application in the Azure entryway.
Explore to https://aka.ms/urlMismatchError to study how to fix this.” while attempting to sign into a SAML-put together single sign-with respect to (SSO) arranged application that has been coordinated with Azure Active Directory (Azure AD).
Anyway, you have a blunder with the How to Fix AADSTS50011? That is alright – it’s simply Azure AD’s validation misbehaving as a result of invalid answer URLs! Since there may be two or three unique explanations behind this mistake, this post likewise portrays several distinct arrangements, that could be useful to you defeated the issues.
The answer url indicated in the solicitation doesn’t match the answer URLs So, when you do a test in your localhost, you can set the answer URL in the AAD App you ought to change the Fix QQQW Files in both App config document and AAD Application Enabling this choice settled my confirmation issue.
The answer URL indicated in the solicitation doesn’t match the answer URLs designed for the application. To tackle the blunder message, since we have the redirect_uri or reply_url. We go to the App How to add the Azure DevOps Hosted Agent IP address to a Cosmos information base firewall.
Problem
Thus, you’re getting a mistake fairly this way:
AADSTS50011: The answer address … doesn’t match the answer addresses designed for the application.
However, why? Did you wreck something? Indeed, if
Reason for getting AADSTS50011
The most ordinary blunder that I have seen, would be “AADSTS50011: The answer address doesn’t match the answer addresses arranged for the application.”
One more variety of this mistake is “How to Fix AADSTS50011: the answer URL determined in the solicitation doesn’t match the answer URLs arranged for the application [guid]”
Definitely, there are a couple phrasings for this mistake!
This blunder can ordinarily be brought about by 2 different setup issues. You’re either (1) getting to the page from an unexpected location in comparison to what you’ve arranged for your application, or (2) you have committed an error in the actual setup. In both of these cases, fixing the issue is ordinarily genuinely simple. You’ll most likely need to simply change the arrangement – how about we perceive how!
Update: Microsoft has consolidated Azure AD v 2.0 endpoints with 1.0, so the entire setup currently occurs in https://aad.portal.azure.com. In the event that you approach your association’s AAD application enrollments, see underneath.
However, in the event that you can alter these authorizations yourself, see two or three things you could check underneath!
Solution(s) to different “The reply address does not match the reply addresses configured” -errors
Microsoft is continually moving kind of thing around in their Azure Active Directory organization site, yet this article presently shows the most recent variant of the application enrollment entryway, that is accessible under https://aad.portal.azure.com
Then again, simply explore to Azure Portal > Azure AD – > App Registrations. See underneath for a model:
In any case, about the fixes – the following are a couple of arrangements that you could attempt:
The straightforward arrangement: Make sure, that your URL is really remembered for the setup
This may be self-evident, I concede, however worth focusing on. Along these lines, this is what to do:
- Peruse to https://aad.portal.azure.com
- Sign in utilizing your Office 365/Cloud App Administrator account
- Explore to “Application enrollments”
- Find your application under “Claimed applications” or “All applications”
- Select “Make due” – > “Verification”
- Check the “Divert URIs” – area and confirm, that the URL you’re getting to the application from truly is recorded there!
There are several things to How to Fix AADSTS50011. As a matter of first importance: is the application id (client id) the equivalent? You’ll have to confirm, that you’re really working on the equivalent application that you’re utilizing on whatever page that tosses the mistake.