Configure User Privileges in NSX Manager for Integration with vRealize Operations Manager in ROBO

Assign the permissions to the service account svc-vrops-nsx that are required to access monitoring data from the NSX Manager in vRealize Operations Manager.

Procedure

Open an SSH connection to the NSX Manager virtual machine.


NSX Manager	Host name
NSX Manager for the ROBO cluster	nyc01r01nsx01.rainpole.local


Setting	Value
User name	admin
Password	`nsx_manager_admin_password`

Create the svc-vrops-nsx local service account on the NSX Manager instance.
1. Run the following command to switch to Privileged mode of NSX Manager.
```
enable
```
2. Enter the admin password when prompted and press Enter.
3. Switch to Configuration mode.
```
configure terminal
```
4. Create the svc-vrops-nsx service account .
```
user svc-vrops-nsx password plaintext svc-vrops-nsx_password
```
5. Assign the svc-vrops-nsx user access to NSX Manager from the vSphere Web Client.
```
user svc-vrops-nsx privilege web-interface
```
6. Commit these updates to the NSX Manager.
```
write memory
```
7. Exit Configuration mode.
```
exit
```

Assign the security_admin role to the svc-vrops-nsx service account.

Log in to the Windows host that has access to your data center.
Run the Postman application and log in.
Select POST from the drop-down menu that contains the HTTP request methods.

In the URL text box next to the selected method, enter the following URL.

NSX Manager	POST URL
NSX Manager for ROBO cluster	https://nyc01r01nsx01.rainpole.local/api/2.0/services/usermgmt/role/svc-vrops-nsx?isCli=true

On the Authorization tab, configure the following authorization settings and click Update Request.


Setting	Value
Type	Basic Auth
User name	admin
Password	`nsx_manager_admin_password`

On the Headers tab, enter the following header details.


Setting	Value
Key	Content-Type
Value	text/xml

In the Body tab, select raw, paste the following request in the Body text box and click Send.

<accessControlEntry>
  <role>security_admin</role>
  <resource>
    <resourceId>globalroot-0</resourceId>
  </resource>
</accessControlEntry>

The Status changes to 204 No Content.