API Description | API Path |
---|---|
List feature permissionsList features |
GET /policy/api/v1/aaa/features-with-properties
|
Get all users and groups with their roles |
GET /policy/api/v1/aaa/role-bindings
|
Delete all stale role assignments |
POST /policy/api/v1/aaa/role-bindings?action=delete_stale_bindings
|
Assign roles to User or GroupWhen assigning a user role, specify the user name with the same case as it appears in vIDM to access the NSX-T user interface. For example, if vIDM has the user name User1@example.com then the name attribute in the API call must be be User1@example.com and cannot be user1@example.com. |
POST /policy/api/v1/aaa/role-bindings
|
Delete user/group's roles assignment |
DELETE /policy/api/v1/aaa/role-bindings/<binding-id>
|
Get user/group's role information |
GET /policy/api/v1/aaa/role-bindings/<binding-id>
|
Update User or Group's roles |
PUT /policy/api/v1/aaa/role-bindings/<binding-id>
|
Get information about all roles |
GET /policy/api/v1/aaa/roles
|
Validate a new feature permission setValidate the permissions of an incoming role. Also, recommend the permissions which need to be corrected. |
POST /policy/api/v1/aaa/roles?action=validate
|
Get information about all roles with features and their permissions |
GET /policy/api/v1/aaa/roles-with-feature-permissions
|
Delete custom roleIf a role is assigned to a role binding then the deletion of the role is not allowed. Precanned roles cannot be deleted. |
DELETE /policy/api/v1/aaa/roles/<role>
|
Get role information |
GET /policy/api/v1/aaa/roles/<role>
|
Clone an already present roleThe role with id the ones provided in the request body. |
POST /policy/api/v1/aaa/roles/<role>?action=clone
|
Update custom roleCreates a new role with id as role with id |
PUT /policy/api/v1/aaa/roles/<role>
|