Note: This article applies only when you attempting to create a RBAC role via API on OPDK (On-prem). Please disregard this if you are trying to create a RBAC role on Edge (via API or UI) and on OPDK (On-prem) via UI.
Once you have created a RBAC role using the API provided at : http://apigee.com/docs/api-services/content/role-based-access-control , you will have to add permissions to role. Below is the minimum set of permissions that have to be set, else it will result in users ( belonging to the role) being unable to log in.
{"path" : "/,"permissions" : [ "get" ]}'
{"path" : "/*","permissions" : [ ]}'
{"path" : "/environments","permissions" : [ "get" ]}
{"path" : "/userroles","permissions" : [ "get" ]}
Setting the above will allow users to be able to login. You can then further add permissions to allow access to Apigee Edge entities based on your requirement. Creating the role via the UI automatically handles the above permissions.
OPDK - How to manually update UI credentials for accessing Management APIs
Accessing Router and Message Processor metrics
Apigee Private Cloud patch 4.15.0.04.03 requires java 7 for UI component
Ansible 101: Apigee Private Cloud Accelerator
4.16.01/4.16.05 Edge Private Cloud doc updates for July 22
Apigee Private Cloud Installation: non-root user
Video of an Edge Private Cloud AIO Install for 4.16.01
Private Cloud (OPDK) Configuration to stream large payloads
Error: Package: apigee-nginx-1.15.6 Requires: libcrypto.so During R/RMP installation of 19.01