memory: sync 2026-04-04 19:57 UTC

This commit is contained in:
Shard
2026-04-04 19:57:48 +00:00
parent ad3d55401f
commit c577d75568
2 changed files with 4 additions and 0 deletions
+3
View File
@@ -50,3 +50,6 @@
- 2026-04-04 18:21 UTC: Keycloak onboarding fix applied live: mapped realm role `player` onto default group `/player` in realm `aeternalis` (group was default but previously had no role mappings), restoring automatic `player` role assignment for new registrations.
- 2026-04-04 18:51 UTC: Heartbeat SOR check — HEAD still e4ddd80; working tree unchanged with M OVERALL.md and M deploy/k8s/ingress.yaml; no SOR hard blocker detected.
- 2026-04-04 18:51 UTC: Argo RBAC hardening applied live: set argocd-rbac-cm `policy.default=role:none` with explicit deny for role:none, retained only /argo-admin and /argo-readonly mappings, cleared local Argo accounts (`accounts.cckbyron/chase/dingo`), and restarted argocd-server successfully.
- 2026-04-04 19:21 UTC: Heartbeat SOR check — no state change since last pass (HEAD e4ddd80; working tree still M OVERALL.md and M deploy/k8s/ingress.yaml). No new blocker or priority change.
- 2026-04-04 19:51 UTC: Heartbeat SOR check — no state change from prior check (HEAD e4ddd80; local M OVERALL.md and M deploy/k8s/ingress.yaml). No new blocker or priority change.
- 2026-04-04 19:57 UTC: Heartbeat SOR check — HEAD advanced to e4ddd80 (store DataProtection keys in Redis for cross-pod cookie decryption). Working tree still has M OVERALL.md and M deploy/k8s/ingress.yaml; no hard blocker detected. High-value next step: validate cross-pod auth/session continuity (login, refresh, restart/rollout) and then reconcile ingress/doc deltas for clean baseline.
+1
View File
@@ -142,3 +142,4 @@ Help Jason ship SOR with low-friction, safe autonomy.
- 2026-04-04 17:57 UTC: Repo head advanced to `e4ddd80` (Redis-backed DataProtection key persistence for SOR.Admin). Priority update: perform RBAC consistency pass in SOR.Admin pages/components to replace legacy `Admin,SuperAdmin` role attributes with the active Keycloak role model (`sor-admin` and any intended tiered roles), then re-validate end-to-end admin access.
- 2026-04-04 18:21 UTC: Live IAM fix completed for onboarding: `/player` default group now maps realm role `player`, so newly registered users should inherit `player` claim automatically. Priority: run one fresh registration smoke test to confirm token contains `player` and SOR auth exchange no longer returns ROLE_REQUIRED.
- 2026-04-04 18:51 UTC: No SOR repo blocker (HEAD `e4ddd80`; local `OVERALL.md` + `deploy/k8s/ingress.yaml` deltas remain). Adjacent platform security action completed: ArgoCD now default-deny RBAC with explicit group grants only (`/argo-admin`, `/argo-readonly`) and local Argo user logins disabled.
- 2026-04-04 19:57 UTC: Repo head advanced to `e4ddd80` (DataProtection keys moved to Redis to prevent cross-pod cookie decryption failures). Working tree remains locally modified in `OVERALL.md` and `deploy/k8s/ingress.yaml`. No hard blocker observed; priority update: run focused multi-pod auth/session resilience validation, then reconcile/commit or clean ingress+doc deltas to restore deploy baseline clarity.