Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Dynamics NAV 2017 Web Client - service tier on a different server to IIS (External)
azman299
Member Posts: 4
Hi all, any ideas would be greatly appreciated.
I have setup the NAV web and mobile client and it works externally ok when the website is running on the same server as the NAV service tier. This is when using Windows under ClientServicesCredentialType.
I need to move the website to a different IIS server - this is where the confusion has started. As mentioned, the web client is available externally using HTTPS.
I installed the web client and changed the web.config and webapplication.config to point over to the internal server hosting the Dynamics NAV service. Firstly trying to use Windows authentication as before, when launching the web client on this server it asks for the login, starts to load the web client then errors out. Event logs point to the fact it cannot find the server hosting NAV.
From my understanding 'UserName' authentication needs to be used here, although this does the exact same thing unless you use Forms authentication in IIS.
When using Forms authentication, it results in some strange behaviour. It brings up the sign in page and after I login with my credentials, it proceeds to login as the user set to run the service tier (Default 'Network Service' if not changed). This happens regardless of which user logs in! This also confirms the servers are communicating also (No firewall blocking etc.)
EDIT: The Universal and mobile client works correctly, even when the web client still only signs in using the service tier user.
As mentioned previously, if I host the web client website on the same machine hosting the NAV service tier this works fine with Windows authentication externally - using localhost in the .config files.
Has anybody come across anything similar? This ones got me extremely confused and I'm most likely doing something silly.
Thanks in advance.
I have setup the NAV web and mobile client and it works externally ok when the website is running on the same server as the NAV service tier. This is when using Windows under ClientServicesCredentialType.
I need to move the website to a different IIS server - this is where the confusion has started. As mentioned, the web client is available externally using HTTPS.
I installed the web client and changed the web.config and webapplication.config to point over to the internal server hosting the Dynamics NAV service. Firstly trying to use Windows authentication as before, when launching the web client on this server it asks for the login, starts to load the web client then errors out. Event logs point to the fact it cannot find the server hosting NAV.
From my understanding 'UserName' authentication needs to be used here, although this does the exact same thing unless you use Forms authentication in IIS.
When using Forms authentication, it results in some strange behaviour. It brings up the sign in page and after I login with my credentials, it proceeds to login as the user set to run the service tier (Default 'Network Service' if not changed). This happens regardless of which user logs in! This also confirms the servers are communicating also (No firewall blocking etc.)
EDIT: The Universal and mobile client works correctly, even when the web client still only signs in using the service tier user.
As mentioned previously, if I host the web client website on the same machine hosting the NAV service tier this works fine with Windows authentication externally - using localhost in the .config files.
Has anybody come across anything similar? This ones got me extremely confused and I'm most likely doing something silly.
Thanks in advance.
0
Answers