You’re offline. This is a read only version of the page.
Hi Experts,
we have NAV 2017 configured on Azure VM with SQL Server also hosted in Azure. The NAV server components are configured to use SSL with a wild card certificate like *.mydomain.co.nz
NAV Server connections are secured using instructions from
NAV application is registered in Azure AD using instructions from
https://docs.microsoft.com/en-nz/dynamics-nav-app/ui-how-register-dynamics-nav-azure
Web client works fine to https://nav.mydomain.co.nz/mynavinstance/webclient
Full client also works fine - both of the above authenticate to Azure AD / Office 365
The Office 365 Outlook add-in for Dynamics NAV works fine...
BUT we can't get the OData service working - we have used instructions from
https://docs.microsoft.com/en-us/dynamics-nav/walkthrough--configuring-web-services-to-use-ssl--soap-and-odata-
When testing the services with a link like https://nav.mydomain.co.nz:7047/mynavinstance/WS/service or a similar OData source we are repeatedly prompted with a login... doesn't get anywhere
I'm wondering if these services also need to be registered in Azure AD to provide authentication?
Any advice/experience on setting up a similar environment would be much appreciated.
*This post is locked for comments
I have the same question (0)
Hi AdamLatJacks,
We faced the same issue in one of our project. To resolve this issue, we created a new Server instance with Windows authentication point to the same database.
Do not use Internet Explorer as it keeps on prompting for login credentials this issue is fixed with Google Chrome.
Share
Report
All responses (
Answers (
3,967
