For assistance with your server credential types please submit a support request with the ODT Technical team for us to work with your IT contact.
Microsoft Dynamics NAV 2016 supports four credential authorization mechanisms for Microsoft Dynamics NAV users. When you create a user, you provide different information depending on the credential type that you are using in the current Microsoft Dynamics NAV Server instance.
 Important |
|---|
| All users of a Microsoft Dynamics NAV Server instance must be using the same credential type. You specify which credential type is used for a particular Microsoft Dynamics NAV Server instance in the Microsoft Dynamics NAV Server Administration tool. |
For more information about how to create users, see How to: Create Microsoft Dynamics NAV Users. Alternatively, you can create new users using the Windows PowerShell cmdlet, New-NAVServerUser. For more information, see Microsoft Dynamics NAV Windows PowerShell Cmdlets.
Credential Types
Microsoft Dynamics NAV supports the following credential types.
| Credential types | Description |
|---|---|
|
Windows |
With this credential type, users are authenticated using their Windows credentials. You can only specify Windows as the credential type if the corresponding user exists in Windows (Active Directory, local workgroup, or the local computer’s users). Because they are authenticated through Windows, Windows users are not prompted for credentials when they access Microsoft Dynamics NAV. |
|
UserName |
With this setting, the user is prompted for username/password credentials when they access Microsoft Dynamics NAV. These credentials are then validated against Windows authentication by Microsoft Dynamics NAV Server. There must already be a corresponding user in Windows. Security certificates are required to protect the passing of credentials across a wide-area network. Typically, this setting should be used when the Microsoft Dynamics NAV Server computer is part of an authenticating Active Directory domain, but the computer where the Microsoft Dynamics NAV Windows client is installed is not part of the domain. |
|
NavUserPassword |
With this setting, authentication is managed by Microsoft Dynamics NAV Server but is not based on Windows users or Active Directory. The user is prompted for username/password credentials when they start the client. The credentials are then validated by an external mechanism. Security certificates are required to protect the passing of credentials. This mode is intended for hosted environments, for example, where Microsoft Dynamics NAV is implemented in Azure. |
|
AccessControlService |
With this setting, Microsoft Dynamics NAV relies on Microsoft Azure Access Control service (ACS) or Azure Active Directory (Azure AD) for user authentication services. ACS is a cloud service that provides user authentication and authorization for web applications and services. ACS integrates with standards-based identity providers, including enterprise directories such as Active Directory, and web identities such as Microsoft account, Google, Yahoo!, and Facebook. For more information, see Authenticating Users with Microsoft Azure Access Control Service. Azure AD is a cloud service that provides identity and access capabilities, such as for applications on Azure, in Microsoft Office 365, and for applications that install on-premises. If the Microsoft Dynamics NAV Server instance is configured to use AccessControlService authentication, you can specify an Azure AD account for each user in the Office 365 Authentication field so that they can access both the Microsoft Dynamics NAV Web client and their Office 365 site. Also, if you use Microsoft Dynamics NAV in an app for SharePoint, users have single sign-on between the SharePoint site and Microsoft Dynamics NAV. For more information, see Authenticating Users with Azure Active Directory. |
|
Important |
|---|
| If Microsoft Dynamics NAV Server is configured to use NavUserPassword or AccessControlService authentication, then the username, password, and access key can be exposed if the SOAP or OData data traffic is intercepted and the connection string is decoded. To avoid this condition, configure SOAP and OData web services to use Secure Socket Layer (SSL). For more information, see Walkthrough: Configuring Web Services to Use SSL (SOAP and OData). |
Configuring the Credential Type
RoleTailored clients and Microsoft Dynamics NAV Server must be configured to use the same credential type.
To edit the configuration for the Microsoft Dynamics NAV Server instance, you can use either the Microsoft Dynamics NAV Server Administration tool or the Microsoft Dynamics NAV 2016 Administration Shell. In the Microsoft Dynamics NAV Server Administration tool, you configure the credential type in the Credential Type field on the General tab. Alternatively, you can edit the CustomSettings.config file. For more information, see Configuring Microsoft Dynamics NAV Server.
|
Important |
|---|
| When Microsoft Dynamics NAV Server services are deployed on Azure, you must configure them on Azure. For more information, see How to: Open Microsoft Dynamics NAV Clients that Connect to Microsoft Dynamics NAV on Microsoft Azure. |
For each Microsoft Dynamics NAV Windows client user, you must modify the ClientUserSettings.config file. The default location for this file is C:\Users\<username>\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\90, where <username> is the name of the user. For the Microsoft Dynamics NAV Web client users, you must modify the web.config file for the Microsoft Dynamics NAV Web Server components. For information, see Configuring Microsoft Dynamics NAV Web Client by Modifying the Web.config File. In the relevant configuration file, find the ClientServicesCredentialType parameter and change the value to one of the options listed earlier.
When you change the credential type for a Microsoft Dynamics NAV Server instance and the relevant client configurations, the changes take effect when you restart the Microsoft Dynamics NAV Server instance and users connect to the instance again.