This article describes how to fix the error “AADSTS500113: no reply address is registered for the application”. You typically get this error, when your app is trying to authenticate your users against Azure Active Directory.
I’ve been posting about different versions of Azure Active Directory authentication errors (different errors with AADSTS -codes) a lot – I’ll need to find a better way to categorize them in the future. But, for now, on to the issue!
Problem
Another day, another app, another reply address -related authentication issue in Azure AD. This one (for once) should be simple.
When you’re loading your app, that’s authenticating against Azure AD, most likely in web browser or other online client, you’ll be redirected to a Microsoft Online login page with the following error:
AADSTS500113: no reply address is registered for the application
This error code is kinda peculiar. It’s not listed on Microsoft’s long list of AADSTS-error codes… Perhaps, because it seems to be a variant of AADSTS50011, which itself has a number of different error messages. These error messages describe different issues with reply URLs – just like this particular error code. I don’t know why, but apparently Microsoft thought that the misconfiguration (not to have reply URLs at all!) deserves a custom error code! It basically looks like “error code AADSTS50011, variant 3” – this just makes me wonder what happened to variants 0, 1 and 2…
Okay, but on to the resolution of the issue. What to do?
Solution to error AADSTS500113
Okay, so you need to add a reply URL. Easy? It should be! Let’s see:
How to verify that your reply URL is included in the Redirect URIs of your app:
- Browse to https://aad.portal.azure.com
- Log in using your Office 365 / Cloud App Administrator account
- Navigate to “App registrations”
- Find your app under “Owned applications” or “All applications”
- Select “Manage” -> “Authentication”
- Check the “Redirect URIs” -section. Verify, that the URL you’re accessing the app from really is listed there!
When accessing the Authentication settings under your app registration, you should add the URLs you expect your app to be called from – like in the screenshot below:
Note: A comparable article – also including an important and interesting hack that you need to try in case the abovementioned trick doesn’t work – is linked below. If this article doesn’t solve your issue, click below.
Hope it helps!
References
- Microsoft has an unfinished list of Azure Active Directory error codes – useful, even if not perfect: https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-aadsts-error-codes
He's been a developer from 2004 (starting with PHP and Java), and he's been bending and twisting SharePoint into different shapes since MOSS. Nowadays he's not only working on SharePoint, but also on .NET projects, Azure, Office 365 and a lot of other stuff. He's also Microsoft MVP for Office Development.
This is his personal professional (e.g. professional, but definitely personal) blog.
- How to fix “System.IO.FileSystem: Could not find a part of the path \AppData\Local\AzureFunctionsTools\Releases\3.17.0\workers. Value cannot be null. (Parameter ‘provider’)” when running Azure Functions locally? - January 12, 2021
- How to nuke the Identity Cache in Visual Studio? - January 11, 2021
- Fixing unexpected Microsoft.AspNetCore package errors after a dependency update - January 6, 2021
