This repository was archived by the owner on Apr 13, 2026. It is now read-only.
Tags: initstring/RTAP
Tags
Disable demo auth when SSO providers are configured (#77) ### Motivation - Prevent the insecure demo login from remaining enabled when any SSO provider is configured, reducing risk of accidental public demo access. - Align provider registration to the validated `env` surface so server-side feature gating uses the same canonical env values. ### Description - Compute `ssoProvidersEnabled` and make `demoModeEnabled` require no SSO in `src/server/auth/config.ts`, and register providers using `env.*` instead of `process.env.*`. - Update the sign-in page `src/app/(public-routes)/auth/signin/page.tsx` to hide the demo button when any SSO provider is enabled by computing `ssoEnabled` and gating `demoEnabled` accordingly. - Add a short note to `docs/installation.md` explaining that demo mode is automatically disabled when any SSO provider is configured. ### Testing - No automated tests were run as part of this change. ------ [Codex Task](https://chatgpt.com/codex/tasks/task_e_696b5fbdbcfc8323ab20ae16f2ea516b)
0.4.2 (#52) ## Summary Addresses potential react2shell vulnerability as well as minor updates. - refresh the frontend/server toolchain dependencies (React Query, tRPC, eslint/tooling, Prisma 6.19, etc.) while keeping the Auth.js stack pinned for manual verification. - update the production `deploy/docker/docker-compose.yml` to reference the new `0.4.2` application image. ## Testing - npm run check - npm run test
feat: evolve crown jewels to more flexible targets (#35) This implements a more generic form of target to include in operations. Previously, there was only "Crown Jewels". Now there are "Targets" with a bool to flag them as Crown Jewels. There are also numerous additional UI components to highlight where assets are targeted in operations and specific techniques, and to better measure the specific outcomes of individual targets.