Skip to content

feat: grant system campaign type decider role to PM administrator - #87

Open
mjfelis wants to merge 1 commit into
mainfrom
feat/admin-system-campaign-roles
Open

feat: grant system campaign type decider role to PM administrator#87
mjfelis wants to merge 1 commit into
mainfrom
feat/admin-system-campaign-roles

Conversation

@mjfelis

@mjfelis mjfelis commented Jul 30, 2026

Copy link
Copy Markdown
Member

Summary

10_PM_ADMINISTRATOR could not see or manage the discovery system campaign: CampaignService.listCampaignVOs gates the DISCOVERY campaign type on the explicit campaign-type-system-* roles (IntrospectionService.getCampaignTypesWithRoles), and the administrator composite only carried campaign-type-system-viewer indirectly via campaign-all-viewer.

This adds campaign-type-system-decider to the 10_PM_ADMINISTRATOR composite in RoleUtil, matching the existing campaign-type-api-decider / campaign-type-ad-decider grants, so administrators can view, edit, and enable system campaigns (e.g. the boot-created "Sim Profile Discovery System Campaign").

Version bumped to 2.83 (CI publishes on merge to main).

Deployment note

After pm-model picks up 2.83, set the BOOLEAN_REGENERATE_KC_ROLES parameter to 1 so KeycloakAdminService rebuilds the role composites in Keycloak, then re-login for the token to include the new role.

10_PM_ADMINISTRATOR only had campaign-type-system-viewer (via
campaign-all-viewer), so admins could not manage the discovery system
campaign. Add campaign-type-system-decider to the administrator
composite, matching the existing API and AD decider grants.

Bump version to 2.83.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant