A customer is planning deployment of a third-party OpenStack application.
Which is used to grant permissions to the application on NSX Manager?
Click on the arrows to vote for the correct answer
A. B. C. D.D.
The Enterprise Administrator role gets the same access to the NSX Manager appliance and the API as the NSX Manager admin user.
The other NSX roles get read-only access to the NSX Manager appliance and the API.
https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.admin.doc/GUID-A8808B7C-799B-4F9A-AA53-To grant permissions to a third-party OpenStack application on NSX Manager, you need to use a Principal Identity.
Principal Identity is an identity source that is used to authenticate users and grant permissions to resources in NSX-T Data Center. It is used to map a user or a group to a role in NSX Manager, which defines the user's access to NSX Manager resources.
When using a third-party OpenStack application, you can create a Principal Identity for the application in NSX Manager. This identity is used to authenticate the application and grant it permissions to the NSX-T Data Center resources it needs to function properly.
Guest Identity and Cloud Identity are not used for granting permissions to a third-party OpenStack application in NSX-T Data Center. Guest Identity is used for authenticating guests in a virtualized environment, while Cloud Identity is used for authentication in cloud environments.
API Identity is used for authenticating and authorizing API clients that access the NSX-T Data Center API. It is not used for granting permissions to a third-party OpenStack application.
In summary, to grant permissions to a third-party OpenStack application on NSX Manager, you should use a Principal Identity.