When setting up a "Dynamics NAV 2013 and later (SQL Server)" data source, one of the authentication methods is "Windows Authentication (other user)".
When would you use this? Would you have two Windows logins on your computer? One for regular stuff and a second one just for NAV?
Thanks.
1 comment
-
Jet Reports Historic Posts Hi Armando -
Great question!
Since the NAV SQL direct connector does not use the NAV client at all, it needs two pieces of information for accessing the NAV data in the SQL database:
#1 What credentials to use for access the data
#2 What credentials to use to set the roles that determine the NAV permissions the individual will have *to* that data
Up to this point, item #2 has always been based on the current Windows user. So, let’s ignore that and focus only on item #1.
With Jet Essentials 2013 and 2013 Update 1, you had the choice of either “Windows Authentication” (for the Windows user who is currently logged in) or “SQL Server Authentication” (a specific username and password). Either of these must be configured by the database administrator in the SQL database itself.
With Jet Essentials 2015, another option was added to allow Windows Authentication for a user *other than* the user who is currently logged in. Thus, if the system administrator had configured the SQL database with a special user (let’s call it “JetReports”) just for use in reporting, Jet Essentials users could set up their data source to use that Windows login.
Keep in mind, item #1 has *nothing* to do with any users set up within NAV. We are strictly talking about accessing a SQL database (which just happens to be a SQL database containing NAV data).
Let's look at an example that might help…
Let’s imagine an organization with 10,000 NAV users – all of whom now have Jet Essentials.
To use 'Current Windows User' Authentication in Jet Essentials, the system admin would have to give the account for every one of those 10,000 users access to the SQL database.
Alternately, the system admin could give *one* user (“JetReports”) access to the database. Then each of those 10,000 users could use 'Other Windows User' Authentication and each of them would use the same username (“JetReports”).
And, the “JetReports” user need not have access to NAV. Because the roles and permissions are determined by the *current* Windows User, each NAV user will automatically have the same roles and permissions applied (when using Jet Essentials) as they do when using NAV.
Make sense?