#SharePointProblems | Koskila.net

Solutions are worthless unless shared! Antti K. Koskela's Personal Professional Blog
>

How to fix an "AADSTS500113: No reply address is registered for the application" error?

koskila
Reading Time 4 min
Word Count 554 words
Comments 17 comments
Rating 5 (2 votes)
View

This article describes how to fix the "AADSTS500113: no-reply address is registered for the application" error. You typically get this error, when your app is trying to authenticate your users against Azure Active Directory.

I have been posting about different versions of the 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, onto the issue!

Problem

Another day, another app, another address-related authentication issue replied 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 a web browser or another 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 kind of 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?

The solution to error AADSTS500113

Okay, so you need to add a reply URL (also called "Redirect URL" or "Redirect URI"). Let's go through the steps to do it in Azure Active Directory:

Time needed: 5 minutes.

How to verify that your reply URL is included in the Redirect URIs of your app?

  1. Browse to https://aad.portal.azure.com

    First, you'll need to navigate to Azure Active Directory Portal (https://aad.portal.azure.com)

  2. Log in using your Office 365 / Cloud App Administrator account

    You'll need to log in using either a Global Administrator, Cloud App Administrator account (or an account that's an owner of the app you want to modify!)

  3. Navigate to "App registrations"

    You should see "App Registrations" in the left hand side navigation.

    App Registrations under Azure Active Directory.
    App Registrations under Azure Active Directory

  4. Find your app under "Owned applications" or "All applications"

    You'll see a list of your applications by default, but if you're not the owner, you can browse all applications by clicking "All applications"

  5. Select "Manage" -> "Authentication"

    Under "Manage" you'll find "Authentication". Click it.

  6. 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:

    "Redirect URIs" -section in Azure Active Directory's app registration view."Redirect URIs" -section in Azure Active Directory's app registration view.

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, see this article instead: How to fix “AADSTS50011: The reply address does not match the reply addresses configured” -error

Hope it helps!

References

Comments

Interactive comments not implemented yet. Showing legacy comments migrated from WordPress.
zainab
2019-10-05 07:22:13)
Really informative article. Worth reading. thanks for sharing...!!
Raymond
2020-10-29 12:44:56)
Hi, I got this error recently. Most of the users do not have the problem but a few have, so I think that does not relate to the Azure configuration issue. The error happen in both iOS and Android. Do you have any idea or what I need to check? P.S. one of the user has signed in successfully but once signed he always got this error and never sign in again with his mobile.
2020-10-30 00:06:10
Hi Raymond, Curious! What are they signing into, if I may ask?
2020-10-31 13:26:49)
YAY! Exactly what I needed!
2020-10-31 22:50:49
Thanks for your comment, Luise - happy to hear it was helpful! 😊
Shweta
2021-10-20 17:31:04)
Thank you Antti for such clear and crisp solutions on various problems which are faced during development.
Antti K. Koskela
2021-10-22 13:16:51
My pleasure, Shweta. 😊
Shweta
2021-10-20 17:41:33)
I am facing several issues when acquiring a token for the Microsoft Graph API.
  1. I have used "adal-angular": "1.0.18" and have successfully received the token for completing Single Sign On.
  2. However when trying to use the same to get the token for Microsoft Graph Resources there are some errors.
  3. Link to the raised queries :
https://stackoverflow.com/questions/69493398/get-the-microsoft-graph-token-with-adal-angular-package-adal-js-authentication-c
Antti K. Koskela
2021-10-22 13:21:28
Hi Shweta, I wonder if you've added all necessary scopes and consented to them? Signing in is indeed one thing, and actually fetching the data a whole another one...
foo
2022-10-26 20:29:44)
I had this issue and confirmed with my IT department many times that the redirectURI was configured correctly in Azure App Services Turns out we needed to add login.microsoft.com to the allowed CORS list After allowing that site the application worked as expected
Antti K. Koskela
2023-03-09 09:59:29
Hi foo and thanks for sharing!