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
- 300 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Authenticate against SOAP / OData w. "UserName"; need separate NAV-instance?
CloudViking86
Member Posts: 6
Hi!
We have a three-tiered setup of NAV 2017 w. authentication for our NAV-instances set to "UserName" where the users authenticate via their AD-credentials.
However when we try to call OData / SOAP (by entering an URL for ex. "SalesOrder") we get an authentication request where the server responds "Digest" and when trying to authenticate using an AD-account which is setup in NAV we get "400 - Bad Request".
Our current setup now is to have a primary instance which users connect to using their AD-account ("UserName") in order to access the RTC and Webclient and another instance in order to be able to use ODATA / Soap that uses "NavUserPassword".
Do we do something wrong when trying to call OData / Soap on our "primary" ("UserName")-instances via an AD-account (which has "Full" rights in NAV) and get "400 - Bad Request" or do you need a separate instance and "UserName" can't be used for OData / Soap?
Thankful for your insights and help
We have a three-tiered setup of NAV 2017 w. authentication for our NAV-instances set to "UserName" where the users authenticate via their AD-credentials.
However when we try to call OData / SOAP (by entering an URL for ex. "SalesOrder") we get an authentication request where the server responds "Digest" and when trying to authenticate using an AD-account which is setup in NAV we get "400 - Bad Request".
Our current setup now is to have a primary instance which users connect to using their AD-account ("UserName") in order to access the RTC and Webclient and another instance in order to be able to use ODATA / Soap that uses "NavUserPassword".
Do we do something wrong when trying to call OData / Soap on our "primary" ("UserName")-instances via an AD-account (which has "Full" rights in NAV) and get "400 - Bad Request" or do you need a separate instance and "UserName" can't be used for OData / Soap?
Thankful for your insights and help
0
Answers
Try switching to the various modes, and try connecting to the SOAP / OData services via internet explorer / microsoft edge. I know IE handles authentication properly, so if you can't login to the URL via IE, then you can blame the service. If it works in IE, you can blame whatever your code calling the SOAP services directly is.