You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 13, 2026. It is now read-only.
Add Keycloak and Okta SSO configuration and sign-in UI (#71)
### Motivation
- Expand SSO support beyond Google so teams can use Keycloak or Okta as
OAuth providers.
- Surface required env variables and documentation so operators can
configure Keycloak/Okta in dev and production environments.
### Description
- Register Keycloak and Okta providers in the NextAuth config and treat
them alongside Google for OAuth validation
(`src/server/auth/config.ts`).
- Extend the server env schema and runtime mapping to include
`KEYCLOAK_*` and `OKTA_*` variables (`src/env.ts`).
- Update the sign-in UI and page to expose provider-specific buttons and
enablement flags for Keycloak and Okta
(`src/features/shared/auth/sign-in-page.tsx`,
`src/app/(public-routes)/auth/signin/page.tsx`).
- Add commented example env entries to `.env.example-dev` and
`deploy/docker/.env.example-prod`, and clarify supported SSO providers
in `docs/installation.md`.
### Testing
- Ran `npm run check` (ESLint + TypeScript checks) which completed
successfully.
- Ran `npm run test` which failed due to Prisma being unable to connect
to a local database (`localhost:5432`), so full test-suite validations
requiring the DB were not executed.
------
[Codex
Task](https://chatgpt.com/codex/tasks/task_e_696b2ca854e08323b6e0bdcf3523c9dd)
Copy file name to clipboardExpand all lines: docs/installation.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,9 +26,9 @@ Minimum values to edit:
26
26
27
27
### Choose authentication mode
28
28
29
-
RTAP supports SSO or a demo login button.
29
+
RTAP supports SSO or a demo login button. Supported SSO providers today are Google, Keycloak, and Okta. If you need another provider, open an issue and we can add it.
30
30
31
-
-**SSO (recommended):** configure your provider's details (like Google client ID/secret) using the variable names provided in the .env file.
31
+
-**SSO (recommended):** configure your provider's details (like client ID/secret + issuer when required) using the variable names provided in the .env file.
32
32
-**Demo mode:** set `ENABLE_DEMO_MODE=true`. This exposes a “Sign in as Demo Admin” button and **anyone with access to the sign-in page can log in without an account**. Use only for isolated testing or demos.
33
33
34
34
For Google SSO, configure the following in the Google Cloud console:
0 commit comments