WebClient Configuration Reply Address

(0) Share

Report

Posted on by Martinho Costa

779

Hello,

I'm configuring dynamics nav 2017 webclient with AccessControlService authentication. When I'm trying to access the webclient I'am getting the following message:

AADSTS50011: The reply address 'softnav.cloudapp.net/.../SignIn.aspx' does not match the reply addresses configured for the application: 'softnav.cloudapp.net/.../WebClient'.

On Azure AD i have the following configuration in a new Application:

Sign-on URL: http://softnav.cloudapp.net:8080/NAV100_CU01_PT1/WebClient/

App ID URI: http://softnav.cloudapp.net:8080/NAV100_CU01_PT1/WebClient/

Reply URL: http://softnav.cloudapp.net:8080/NAV100_CU01_PT1/WebClient/

With same settings I'm not having any issue on 2016.

Any ideia?

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

AJAnsari 5,754 on at

Like (0)

Report
Copy link

Link copied!

Hi Martinho,

Seeing as how you haven't received any responses yet, I suppose it can't hurt to throw a couple things at the wall and see if anything sticks.

Suggestion #1:

In the NAV Administration tool (where you manage NAV services), have you checked the NAV100_CU01_PT1 service > Client Services > Web Client Base URL field to see that the URL contains the ":8080" after softnav.cloudapp.net? I would also advise that you ensure there is a preceding "http://" as well, if you don't have it there already.

To make things even easier, ensure that this field contains exactly the same URL as what you have in the Reply URL in Azure AD: softnav.cloudapp.net/.../WebClient

If you had to change anything, you might want to restart the NAV service before trying again.

That port 8080 reference is a key difference between the Reply URL in Azure AD and the the Reply address show in the error.

Suggestion #2:

If that doesn't work, it doesn't hurt to try changing the Reply URL in Azure AD so that it doesn't include ':8080'. Frankly, I doubt Suggestion #2 will work.

If all else fails, it may be time to open a support case with Microsoft.

Hope I was able to help.

Was this reply helpful? Yes No
CDsilva 4,188 on at

Like (0)

Report
Copy link

Link copied!

Hi Martinho,

Did you find a solution to your error?

I'm facing the same error. Kindly post your solution.

Was this reply helpful? Yes No
Martinho Costa 779 on at

Like (0)

Report
Copy link

Link copied!

Hey Chris... No, Still have the same issue.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hey Guys,

I was experiencing the same thing.

I had to add the -NAVWebAddress switch specifying the NAV Web Client address when executing the 'Set-NAVSingleSignOnWithOffice365' command in PowerShell. It is similar to what Anil has posted here: https://community.dynamics.com/nav/b/dynamicsnavcloudfronts/archive/2017/06/02/set-up-single-sign-on-in-dynamics-nav-with-office-365-using-windows-powershell. If you look at the command in Step 9 you will see it there.

Regards,

David.

Was this reply helpful? Yes No
Suggested answer

CDsilva 4,188 on at

Like (0)

Report
Copy link

Link copied!

Hi Martinho

I fixed my issue, you can refer my blog

www.cloudfronts.com/error-resolution-web-client-reply-address-sso-dynamics-nav

Was this reply helpful? Yes No
Tina Menezes 2,582 on at

Like (0)

Report
Copy link

Link copied!

Hi Martinho

You can check my blog on configuring SSO using the below link to verify if you have performed all steps:

tinamenezesdynamicsnavblog.wordpress.com/.../set-up-single-sign-on-in-dynamics-nav-with-office-365-using-windows-powershell

Kindly check if your certificate thumbprint is appropriate and binding is done as well.

Was this reply helpful? Yes No