NAV 2017 not documented options for “Credential Type”


In NAV 2017 there are two new options for “Credentials Type”: TaskScheduler and EchangeIdentity.

“Credential Type” -> “AS IS” Documentation
“Specifies the authentication mechanism for Microsoft Dynamics NAV users of this Microsoft Dynamics NAV Server instance.”
The options are “Windows, Username, NavUserPassword, and AccessControlService”.

But… What about others features ?  “TaskScheduler”, “EchangeIdentity”, “None” ?

In reality now there are three not documented options in the online help and also in NAV admin console help: “TaskScheduler”, “EchangeIdentity”, “None”   …the option “None” was already existing in 2016, undocumented.

NAV 2016

nav-2016-1

NAV 2017

nav-2017-2

nav-2017-3

I asked Microsoft to update the documentation on MSDN (not updated from NAV 2016), useful in explaining exactly the “scope” and the “ByDesign” concept of each option.  I’ll let you know!  .

I have the solution (23/03/2017..) !.. Thanks to Microsoft…  -> “These options are for Dynamics 365 for Financials” .. IASS applications !!!  .not for NAV.

MSDN – “Users and Credential Types”
https://msdn.microsoft.com/en-us/dynamics-nav/users-and-credential-types

 

Some old posts

I have already talked about the new task scheduler and new NAV Admin console options previously, below some links that can be useful.

NAV 2017 “Task Scheduler”
https://robertostefanettinavblog.com/2016/11/04/nav-2017-task-scheduler/

NAV 2017 – What’s new in the Administration Console
http://www.pakiki.info/2016/11/01/nav-2017-whats-new-in-the-administration-console/

How to force specific service instance in Task Scheduler in NAV 2017?
http://forum.mibuso.com/discussion/68576/how-to-force-specific-service-instance-in-task-scheduler-in-nav-2017

Advertisements

How To setup “Keep Alive Interval” setting NAV2016-NAV2017


Many posts in forums about this topic; some people report that Idle Client Timeout configured in NAV Administration is not working.
Example of scenario: “Users logs in to the Navision by windows client installed on their PC but after setting idle client timeout session for 3 minutes then also it does not log off after 30 minutes also.”
or
Automatically Idle Client Timeout – NAV2016 – doesn’t work!
http://forum.mibuso.com/discussion/66081/automatically-idle-client-timeout-nav2016-doesnt-work

History of ClientKeepAlive setting
Since the October 2015 cumulative updates, the Dynamics NAV Windows client timeout configuration was managed at the service level by setting the Idle Client Timeout setting.

“The October 2015 cumulative updates added a new setting: “ClientKeepAlive”.
This  setting is managed at the user level and located in the ClientUserSettings.config file.

The value of this setting is given in seconds and defines the interval between ‘pulse’ signals sent by the client to prevent the client from going idle in some scenarios, or for some users.

ClientKeepAlive: about this setting

  1. In the server configuration file, set Idle Client Timeout  to 00:10:00
  2. In the client configuration file, set ClientKeepAlive  to any value  larger than 600
    This value is in seconds, so 600 equals 10 minutes.

Microsoft, by popular demand, changed in Dynamics NAV 2016 Cumulative Update 8:
The ClientKeepAlive setting has been moved from the user level to the service level: “Keep Alive Interval “, and is no longer defined in number of seconds but as a time interval, just like the Idle Client Timeout setting.”

Keep Alive Interval : about this setting

So following our example above, to configure a timeout interval for the Dynamics NAV Windows client to 10 minutes, in Dynamics NAV 2016 Cumulative Update 8 and later, you must set the following:

  1. In the server configuration file, set Idle Client Timeout  to 00:10:00
  2. In the server configuration file, set Keep Alive Interval  to a value larger than 00:10:00

PS: If you are running on a NAV 2016 build earlier then CU 8, your clientkeepalive settings will still be located Client side, in ClientUserSettings.config

Web Client
“To configure the timeout for the Dynamics NAV Web client, it is sufficient to configure the SessionTimeout setting in the web.config file to the relevant interval – in our example it’s 00:10:00.”

PS: Check your NAV Release and build for correct configuration!

Sources:
Configuring Client Timeout
https://blogs.msdn.microsoft.com/nav/2016/06/24/configuring-client-timeout/

Understanding Session Timeouts NAV 2016-NAV 2017
https://msdn.microsoft.com/en-us/library/dn789725(v=nav.90)