Jet Remote Data Source (JRDS) access
By default, all users are authorized to access the JRDS. The full set of allowed and denied users can be viewed with the Get-JetRemoteDataServiceInstance command and noting the values shown for Authorized Users, Authorized Groups, Denied Users, and Denied Groups.
Through the use of Set-JetNavRemoteDataServiceInstance and Set-JetGpRemoteDataServiceInstance , both the Dynamics NAV and Dynamics GP Remote Data Sources allow the JRDS administrator to configure user, and group, authorization rules to individual JRDS instances within Windows Internet Information Services (IIS). The additional Set- command parameters are:
|-CreateAuthorization||Parameter used in the Set- command to initiate the process of creating IIS authorization rule(s).|
Whether a user, or role (i.e., “group”) is subject to the authorization rule.
Accepted values are 0 and 1
Whether to allow, or deny, access to the JRDS instance provided.
Accepted values are 0 and 1:
The name of the user or role subject to the authorization rule.
The Value should be domain-prefixed, if applicable (e.g., “DOMAIN\USERNAME”)
The following examples use the Set-JetNavRemoteDataServiceInstance , but will work just the same via Set-JetGpRemoteDataServiceInstance .
Let's look at an example where we want to allow the username "SDV" to have access to the "JetReports" JRDS instance.
Set-JetNAVRemoteDataServiceInstance -InstanceName "JetReports" -CreateAuthorization -AuthorizationType 0 -AccessType 1 -AuthorizationName mydomain\sdv
Let's now look at an example where we remove the "All Users" access to that same instance:
Set-JetNAVRemoteDataServiceInstance -Instance JetReports -CreateAuthorization –AuthorizationType 0 –AccessType 0 –AuthorizationName *
We now see that the implicit access for "All Users" has been removed and that group is now denied access, and only the user "SDV" has authorization to connect to the JRDS:
Configuring the Data Source
When using a JRDS Data Source to access Dynamics NAV information and your NAV installation is configured to use an authentication type *other than* Windows Authentication, you will need to specify the Windows Authentication information that has been configured in the JRDS itself.
Given the above example where the user "SDV" on the domain "mydomain" has been granted JRDS access, the data source in Jet Essentials might be configured like this: