NOTE: The Hybrid Cloud Console RBAC service is required for integrating with the HCC platform. Without using the HCC RBAC model, anyone with a valid certificate and credentials to access the account can view all information associated with the Organization. 

Purpose (the why):

• In order to enforce role-based access control for authorization against your service, you must define roles and permissions for organization administrators to assign to users within their org.

Responsible:

• App Team Developers, App Team Engineering Manager, App Team Product Manager

Next task: 

• After roles/permissions are seeded into RBAC, enforcement should be pushed from the service.

Deliverable/completion criteria: 

• The steps outlined in the App Team RBAC Integration and Enforcement are complete. 
• You have defined your default state (are you deny by default?)
• You have reviewed the RBAC guidelines and specifications and completed integration into the API. 

Expected duration/effort:

• Config/seed changes can be completed the same day, but generally, we would ask for a sprint so that we can schedule the changes into our existing workload. 

Due date: 

• First deployment to a pre-production environment.

Supporting documentation/best practices: 

• App Team RBAC Integration and Enforcement
• HCC Platform RBAC
• RBAC Config

Exception process:

• A valid business reason must be provided and an exemption can only be received from Lindani Phiri 

How to get help:

• Contact kwalsh@redhat.com or rhn-support-cmitchel (engineering)