Prisma Cloud Application Security :Custom Role doesn't show under "Repositories" or "Technologies" view
Symptom
• The affected user reported that repositories and technologies did not appear in the "Repositories" and "Technologies" views, despite correctly appearing in the "Projects" view.
• The user noticed that the problem persisted even after applying filters in the "Repositories" and "Technologies" views.
• The behavior suggested a potential bug within either the Prisma Cloud UI or backend, causing issues with displaying restricted content based on custom roles.
• The affected user reported that repositories and technologies did not appear in the "Repositories" and "Technologies" views, despite correctly appearing in the "Projects" view.
• The user noticed that the problem persisted even after applying filters in the "Repositories" and "Technologies" views.
Environment
• Prisma Cloud - Application Security
Cause
Unfortunately GRBAC (Custom roles) aren't supported by the CICD pages (aka Repositories page).
In order to create a role with specific repositories permission and to see only the selected repositories on both of Repositories and Projects page - one can add a new role with Permission group: Account and Cloud Provisioning Admin and select the relevant repositories.
Regarding the projects page- the custom role is supported in the Projects page , and that's why the user can see his repositories under the custom role.
Resolution
Product limitation.