The Microsoft Dynamics NAV Universal App can only run on an HTTPS protocol. To enable support for HTTPS on Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client, you must implement security certificates. Complete instructions are available from your certificate provider. We recommend that you secure the data that is transmitted over the Internet by enabling Secure Sockets Layer (SSL) on the connection to the Microsoft Dynamics NAV Universal App. For more information, see Digital Certificates.
The following table illustrates how SSL is enforced.
| Mode | Credentials Type | Enforced SSL? |
|---|---|---|
Microsoft Dynamics NAV Universal App | Windows authentication | Enforced |
NavUserPassword | Enforced | |
Microsoft Dynamics NAV Tablet client and Microsoft Dynamics NAV Phone client in a browser | Windows authentication | Not enforced Only credentials are encrypted, all other communication over the network is sent in clear text. Use SSL to help secure this. |
NavUserPassword | Not enforced Credentials in addition to all other communication over the network are sent in clear text. Use SSL to help secure this. |
Implementing Security Certificates
Microsoft Dynamics NAV Universal App only works using an HTTPS protocol. This means that you must configure a valid certificate on the server. If a trusted, valid, and signed certificate is configured on the Microsoft Dynamics NAV Server, the end-user does not have to do anything. If a self-signed certificate is configured on the Microsoft Dynamics NAV Server, the end-user must install a certificate on their device. The steps for implementing certificates will vary depending on the platform the user is using.
For more information, see How to: Implement Security Certificates in a Production Environment and How to: Create a Self-signed Security Certificate Using PowerShell Script.
 Important |
|---|
| It is recommended to only use self-signed certificates for testing purposes and never in a production environment. |