NWUI: AD/LDAP user who is not defined in NetWorker can review the dashboard.

Summary: External authentication (AD/LDAP) has been integrated with NetWorker. AD/LDAP users or groups have been integrated NetWorker roles; however an external user who has not been given any permissions in NetWorker can log in to NWUI and review the dashboard. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

AD/LDAP has been integrated with NetWorker. The NetWorker external authority integration does not have a user search path or group search path specified (global read-access):

user and group search paths are not set in the networker external authority resource

AD/LDAP users, or groups have been added to the external roles fields of Server->User Groups. An AD/LDAP user does not belong to any of the groups defined in NetWorker, and the user is not defined in any of the NSR usergroups.

NOTE: See the Additional Information section for instructions on verifying the NetWorker permissions defined in an environment, and how to see what AD/LDAP users belong to which AD/LDAP groups.

The AD/LDAP user can log in to the NetWorker Web User Interface (NWUI) and can see the Dashboard and Monitoring tabs:

AD user logged into NWUI

The user is not able to review or change the NetWorker configuration; however, they can access information about completed or running jobs on the NetWorker server:

NWUI running sessions as viewed by unprivileged external user

Cause

This issue has been raised to NetWorker engineering. NetWorker is working as designed. If no user search path or group search path is specified NetWorker authc has global read-access to the entire AD/LDAP structure. 
This may also be observed if a user search path and/or group search path has been set, but it is set to low within the AD/LDAP structure, allowing subtree search to pickup users/groups below the path set.

Resolution

Restrict NetWorker's visibility of the AD/LDAP organization to only users/groups which should have access to NetWorker. This can be done using the user search path and group search path fields in the NetWorker external authority resource.

  1. In the AD/LDAP environment, identify the Distinguished Name (DN) of the parent Container (CN) or Organization Unit (OU) that require NetWorker access.

For example, The following PowerShell command can be used to identify the location of a group within Microsoft AD:

Get-ADGroup -Identity "GROUP_NAME" | Select-Object -Property Name,ObjectClass,DistinguishedName
Example:
PS C:\Users\Administrator> Get-ADGroup -Identity "NetWorker_Admins" | Select-Object -Property Name,ObjectClass,DistinguishedName

Name             ObjectClass DistinguishedName
----             ----------- -----------------
NetWorker_Admins group       CN=NetWorker_Admins,OU=DELL,DC=networker,DC=lan

In this example, we can see that the group belongs under the Organization Unit (OU) OU=DELL,DC=networker,DC=lan. The group's OU/CN can be used as the group search path.


The following PowerShell command can be used to get the location of Microsoft AD users within an AD group:
Get-ADGroupMember -Identity "GROUP_NAME" | Select-Object Name, SamAccountName, ObjectClass, DistinguishedName

Example:

PS C:\Users\Administrator> Get-ADGroupMember -Identity "NetWorker_Admins" | Select-Object Name, SamAccountName, ObjectClass, DistinguishedName

Name                         SamAccountName ObjectClass DistinguishedName
----                         -------------- ----------- -----------------
NetWorker Engineering        nwree          user        CN=NetWorker Engineering,OU=DELL,DC=networker,DC=lan
Backup Administrator         bkupadmin      user        CN=Backup Administrator,OU=Support_Services,OU=DELL,DC=networker,DC=lan
In this example, we can see that users in the group may exist in more than one location; however, in this case, both users belong under the OU OU=DELL,DC=networker,DC=lan. The user's OU/CN can be used as the user search path.

NOTE: You must consider subtree resources. For example if there are other OU/CN under the path selected, they will also be visible to NetWorker. This can be used to grant permissions to users/groups under a specific path; conversely, it also opens access up to groups/resources beneath a specified path. For assistance in getting the appropriate user and group search paths, consult with your domain administrator.
  1. Log in to the NetWorker Web User Interface (NWUI) using the default NetWorker Administrator account.
  2. Go to Authentication Server->External Authority.
  3. Select the external authority resource and click EDIT.
  4. From the external resource properties, go to the ADVANCED CONFIGURATION tab.
  5. Update the Group Search Path and User Search Path fields to include the OU/CN path (excluding DC values) to the parent OU/CN resource you want NetWorker authc to have read-access to.
Update the group search path and user search path fields to contain the AD resources
NOTE: Any group/user under the search paths specified can access NWUI. Any user/group outside of the path specified does not have access, even if User Group permissions have been granted.
  1. Go to the BASIC CONFIGURATION tab.
  2. In the User DN Password field, enter the password of the User DN account.
  3. Click SAVE. The resource reports if it is updated successfully:
External authority resource updated successfully

Users/groups who reside under the group search path and user search path specified will still be able to log in to NWUI; however, users who reside outside these paths will not be permitted NWUI access.

unauthorized user is not permitted

Additional Information

On the NetWorker server, verify what external users/groups are defined in NetWorker user groups:

nsradmin
show name; external roles
print type: nsr usergroup

nsradmin nsr usergroup external roles

An external user can be found by authc; however, is not a member of any of the groups defined in the NSR usergroup external roles fields; nor is the user-defined in any of these fields:

On the NetWorker authentication server, verify the AD/LDAP groups that a user belongs to.

authc_mgmt -u Administrator -p 'NETWORKER_ADMINISTRATOR_PASSWORD' -e query-ldap-groups-for-user -D query-tenant=TENANT_NAME -D query-domain=DOMAIN_NAME -D user-name=USER_NAME

authc_mgmt command to show users group membership on external auth server

In this instance the user testuser2 is not a part of the NetWorker_Admins AD group set in the NSR usergroup external roles fields, nor is the user DN defined in the external roles fields.

Affected Products

NetWorker

Products

NetWorker Family
Article Properties
Article Number: 000252854
Article Type: Solution
Last Modified: 13 Dec 2024
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.