Skip to content

feat: draft, publish and roll back auth policy changes #402

Description

@Bccorb

Why

Policy changes take effect immediately today. Self-hosters cite this as how Keycloak deployments lock out every user.

What

  • Policy-affecting system config changes can be saved as a draft
  • Publish applies them atomically; every published version is kept
  • Roll back to any previous version in one step
  • Audit each step

Done when

A policy change can be reviewed before it applies and undone in one step.

Activity

  1. added this to the v0.20 milestone on Oct 13, 2026
  2. added
    P2GovRAMP readiness track
    safeServes the safe promise: no lockout, no lock-in, honest
    v0.20Targets the v0.20 release
    on Oct 13, 2026
  3. added theissue type on Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2GovRAMP readiness tracksafeServes the safe promise: no lockout, no lock-in, honestv0.20Targets the v0.20 release

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions