-
- Expert
- Posts: 172
- Liked: 20 times
- Joined: Oct 03, 2016 12:41 pm
- Full Name: Robert
- Contact:
Modern authentication restore reirect URL - How to?
Hi,
Trying to restore to O365 using modern authentication. I can proceed throught the login process, but ends up with:
AADSTS500113: No reply address is registered for the application.
This means the APP is missing a redirect URL configuration (under authentication -> Add a platform). But whatever i try, i get different errors.
How do i configure the redirect URL correct i AAD?
/Robert
Trying to restore to O365 using modern authentication. I can proceed throught the login process, but ends up with:
AADSTS500113: No reply address is registered for the application.
This means the APP is missing a redirect URL configuration (under authentication -> Add a platform). But whatever i try, i get different errors.
How do i configure the redirect URL correct i AAD?
/Robert
-
- Veeam Software
- Posts: 3195
- Liked: 774 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Modern authentication restore reirect URL - How to?
Hi Robert,
The configuration steps are covered by Microsoft here: https://docs.microsoft.com/en-us/azure/ ... gistration
When creating apps automatically, VBO adds the http://localhost/ as a redirect URI, but you can choose to configure the 'nativeclient'. Technically, there will be no difference, either of those should do the job.
Thanks!
The configuration steps are covered by Microsoft here: https://docs.microsoft.com/en-us/azure/ ... gistration
When creating apps automatically, VBO adds the http://localhost/ as a redirect URI, but you can choose to configure the 'nativeclient'. Technically, there will be no difference, either of those should do the job.
Thanks!
-
- Expert
- Posts: 172
- Liked: 20 times
- Joined: Oct 03, 2016 12:41 pm
- Full Name: Robert
- Contact:
Re: Modern authentication restore reirect URL - How to?
Thank you - that worked.
Client type (Treat application as a public client) has to be set to YES.
Client type (Treat application as a public client) has to be set to YES.
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Oct 01, 2020 12:34 pm
- Full Name: James Welburn
- Contact:
Re: Modern authentication restore reirect URL - How to?
Hey, sorry to ressurect, but i'm having the same error. Is that public setting all you had to change? I have done this but it still gives the same error. Does it take a while to apply?
-
- Expert
- Posts: 172
- Liked: 20 times
- Joined: Oct 03, 2016 12:41 pm
- Full Name: Robert
- Contact:
Re: Modern authentication restore reirect URL - How to?
What i did was to run the "add organization" once more, the same organisation without removing the existing one, and chosed "register a new Azure application automatically".
I called the "new" Azure APP TEST, which it created, and then ended up with the error "the organisation cannot be created, it already exists".
I then verifed the settings on the new TEST veeam app and saw Client type (Treat application as a public client) was set to yes So i set the Azure APP, i had manually created to the sa,e value, deleted the TEST app Veeam created and then it worked. The APP access rights was the same, so i guess something else was created/set duting Veeams auto setup wizard, i did not create.
I called the "new" Azure APP TEST, which it created, and then ended up with the error "the organisation cannot be created, it already exists".
I then verifed the settings on the new TEST veeam app and saw Client type (Treat application as a public client) was set to yes So i set the Azure APP, i had manually created to the sa,e value, deleted the TEST app Veeam created and then it worked. The APP access rights was the same, so i guess something else was created/set duting Veeams auto setup wizard, i did not create.
-
- Veeam Software
- Posts: 3195
- Liked: 774 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Modern authentication restore reirect URL - How to?
While it's not possible to add the same organization twice, you can add an existing one and change what's needed, i.e. auth method and the app to be used.
The key things to configure for an application (besides permissions):
1) In the App registrations -> Authentication -> Advanced, set the 'Treat application as a public client' to 'Yes'
2) In the App registrations -> Authentication -> Mobile and desktop applications -> set a redirect URI to either the http://localhost/ the 'nativeclient'.
Usually these changes are applied instantly, but sometimes things happen with O365
The key things to configure for an application (besides permissions):
1) In the App registrations -> Authentication -> Advanced, set the 'Treat application as a public client' to 'Yes'
2) In the App registrations -> Authentication -> Mobile and desktop applications -> set a redirect URI to either the http://localhost/ the 'nativeclient'.
Usually these changes are applied instantly, but sometimes things happen with O365
Who is online
Users browsing this forum: No registered users and 15 guests