Skip to content
SHC Docs

Ruling: auto-redirect SSO is the corp/prod default across flagship, 2026-08-14

Owner, 2026-08-14 (after the wazuh role-mapping fix proved his SSO login): “flip the auto redirect, make sure all the flagship apps support that and it’s what i want by default at least for my bitspur and promanager ops clusters … for the prod environment … in the corp tenant.”

  1. Scope: the corp tenant’s prod environment on both production estates (bitspur, promanager). Wider defaults are not ruled here.
  2. Every flagship app must SUPPORT auto-redirect SSO: an SSO-capable flagship app whose package cannot be armed (edge flavour, native knob, or equivalent) is a package gap to fix, not an accepted state.
  3. Auto-redirect is the DEFAULT POSTURE in that scope, armed via the global ssoAutoRedirect flip (already true on both estates) plus each app’s native knob where the app carries one (wazuh’s keycloak.autoRedirect, nextcloud’s user_oidc allow_multiple_user_backends=0).
  • Nextcloud (R2): SHC still never arms it; its auto-redirect rides its own user_oidc config, live on both estates. The outcome (auto-redirect) satisfies this ruling; the mechanism stays app-native.
  • Escape hatches stay: ?sso=false / ?direct=1 style escapes and the loop guards are part of the posture, never removed to arm.
  • Never remove a fallback before the primary is proven; wazuh’s password form was removed only after the owner’s SSO login verified the full role chain (the 2026-08-14 role-mapping fix: realm role wazuh-admin → client roles claim → roles_key → all_access). The same proof precedes arming any app whose knob removes local login.

Wazuh role-mapping recipe (reusable for OpenSearch-family apps)

Section titled “Wazuh role-mapping recipe (reusable for OpenSearch-family apps)”

The oidc plug wires authentication only; authorization is operator territory: realm role → protocol mapper emitting top-level roles claim on the app’s client → dashboard roles_key: roles → backend role merged into all_access via PATCH _plugins/_security/api/rolesmapping/all_access (read-merge, never clobber). Owed: fold this into the wazuh package as an integration job so the next estate doesn’t rediscover it.

  • wazuh: keycloak.autoRedirect=true re-rendered on both estates’ corp/prod.
  • A flagship-wide audit/arming pass over corp/prod on both estates follows (workflow lane flagship-autoredirect): per-app verdict (armed / armed now / package gap) with far-side 302 proofs and the gap list feeding package fixes.