User can add Active Directory(AD) groups via CLI and login to OnCommand System Manager with a user account which is part of this AD group using AD/username & credentials
Steps:
- The security login create command creates a login method for the management utility.
- Add application type as ontapi (for executing ZAPI) and http (for web service requests)
- For System Manager, role can be admin or read-only, custom roles are not supported.
- authentication method as domain
1.a) Security login create command example, with AD group name as smqa-tme and AD as smqa
- security login create -user-or-group-name smqa\smqa-qa -application ontapi -authentication-method domain -role admin
- security login create -user-or-group-name smqa\smqa-qa -application http -authentication-method domain -role admin
- Use security login show command to view the output
F8080-32-22-25::> security login show -user-or-group-name smqa\*
Vserver: F8080-32-22-25
Second
User/Group Authentication Acct Authentication
Name Application Method Role Name Locked Method
-------------- ----------- ------------- ---------------- ------ --------------
smqa\smqa-tme http domain admin - none
smqa\smqa-tme ontapi domain admin - none
smqa\smqa-tme ssh domain admin - none
3 entries were displayed.
- Log in to OnCommand System Manager with active directory username and credentials. In this example: Nikhil has been added as a user to group smqa-qa and the Active directory is smqa.
Username: Smqa/Nikhil password : relevant passowrd
Figure 1 Login to System Manager via AD\username
- Nikhil can login to System Manager , Nikhil will have admin access as a user who is part of AD group , smqa-qa.
- Navigate to Settings in top right corner followed by Users, added AD group from CLI can be viewed from System Manager
Figure 2: Settings>Users
Warning!
This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.
In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:
- Software files (compressed or uncompressed)
- Files that require an End User License Agreement (EULA)
- Confidential information
- Personal data you do not want publicly available
- Another’s personally identifiable information
- Copyrighted materials without the permission of the copyright owner
Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.
