Redirect URL for WebClient (2018) not working / Adding multiple subsites (1 per NAV-instance)

CloudViking86

NAV version: Dynamics Nav 2018 11.0.19394.0
IIS: v. 10
OS: Win Srv 2016

Hello,

Running into what I think is a weird error when trying to deploy multiple subsites (1 per NAV-instance), this is our setup now in the IIS:

One "Application Pool" that both the "Microsoft Dynamics NAV 2018 Web Client" and "Microsoft Dynamics NAV 2018 Help" is using.
Under the "Microsoft Dynamics NAV 2018 Web Client" we have two "applications";
OurNavInstance1
OurNavInstance2
these in turn have the physical path of "C:\inetpub\wwwroot\OurNavInstance1" and "...\OurNavInstance2" and the virtual path of "/OurNavInstance1" and "/OurNavInstance2".

---> App Pool
--> Site
-> OurNavInstance1
-> OurNavInstance2
etc.

Externally (Trying to use the frontfacing URL):
https://external-facing-url.com/OurNavInstance2/webclient/signin.aspx
(redirects me to after login)
https://external-facing-url.com/?signInRedirected > "403 - Forbidden: Access is denied. You do not have permission to view this directory or page using the credentials that you supplied."

If I append "OurNavInstance2/SignIn?ReturnUrl=%2Fournavinstance2%2F" to the URL above then I automatically get into NAV since I auth:ed earlier however this is not something I want for our end-users naturally.

Internally (on the IIS-server when browsing the "OurNavInstance2"-application):
http://localhost:xxxx/OurNavInstance2/SignIn?ReturnUrl=/ournavinstance2/
(redirects me to after login)
http://localhost:xxxx/OurNavInstance2/ > Works

I've followed the documentation here:
https://docs.microsoft.com/en-us/dynamics-nav/how-to--set-up-multiple-web-server-instances-for-the-microsoft-dynamics-nav-web-client

Now forgive my ignorance of the IIS, for NAV 2017 we didn't have any issues setting up a virtual directory which in turn contains one "application" and then we had:
https://external-facing-url.com/OurNavInstance1/webclient/signin.aspx
https://external-facing-url.com/OurNavInstance2/webclient/signin.aspx
https://external-facing-url.com/OurNavInstance3/webclient/signin.aspx
and so on and login and logout works perfectly.

Would be happy to provide any other information you would need to help and do appreciate your help.

robintheswede

Not sure what the issue actually is, please describe more clearly. Are you giving the users an URL which looks like https://external-facing-url.com/?signInRedirected ?? In NAV2018 you should only give them https://external-facing-url.com/OurNavInstance2 not even with the WebClient ending. The base URL for the web client is shorter for NAV2018 than NAV2017.

tcannervall

Hopefully someone can shed some light to this problem. I'll try to expand on the previous error report

In 2017 the NAV webclient URL:s are as following

https://external-facing-url.com/OurNavInstance1/webclient/signin.aspx
https://external-facing-url.com/OurNavInstance2/webclient/signin.aspx
https://external-facing-url.com/OurNavInstance3/webclient/signin.aspx

But in 2018 they aren't set up like that.

Trying

https://external-facing-url.com/OurNavInstance1
https://external-facing-url.com/OurNavInstance2
https://external-facing-url.com/OurNavInstance3

Won't work. The page can't be reached. It however seem to do somekind of redirect so that it acctually tries to contact

http://external-facing-url.com/ournavinstance1/SignIn?ReturnUrl=/ournavinstance1/

Trying directly to access it from IIS or by browsing the page that the login is located at is

https://external-facing-url.com/ournavInstance1/SignIn?ReturnUrl=/ournavinstance1/
https://external-facing-url.com/ournavInstance2/SignIn?ReturnUrl=/ournavinstance2/
https://external-facing-url.com/ournavInstance3/SignIn?ReturnUrl=/ournavinstance3/

Trying this exakt URL works. But it's not ideal. Since it automatically changes to this if you go through the IIS I guess this is somewhere put as default login page but can't find any information on this

In our case we have the actual NAV instances on one server and the IIS on another if that can be of importance

Anyone with any ideas to this behaviour is gratly appriciated