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
* Add Google OAuth sessions and team access UI
* Fix OAuth review issues and e2e CORS
* Fix team access review bugs
* Gate destructive Prisma sync
---------
Co-authored-by: chris <chris@chrisdeMac-mini.local>
-`AUTH_TOKEN` — bearer token expected by the API and CLI clients
31
-
-`VIEWER_ASSERTION_SECRET` — HMAC secret used to verify signed viewer assertions for trusted impersonation
35
+
-`APP_ORIGIN` — browser origin used for cookie/CORS handling and post-login redirects
32
36
-`PORT` — API port (defaults to `4200`)
33
37
38
+
Optional but recommended server variables:
39
+
40
+
-`AUTH_TOKEN` — trusted bearer token used by the CLI and local/dev bootstrap flows
41
+
-`VIEWER_ASSERTION_SECRET` — HMAC secret used to verify signed viewer assertions for trusted impersonation
42
+
-`GOOGLE_OAUTH_CLIENT_ID` — Google OAuth client id for browser sign-in
43
+
-`GOOGLE_OAUTH_CLIENT_SECRET` — Google OAuth client secret
44
+
-`GOOGLE_OAUTH_REDIRECT_URI` — Google callback URL handled by the API server
45
+
-`GOOGLE_OAUTH_ADMIN_EMAILS` — comma-separated allowlist of emails that should become `ADMIN`
46
+
-`SESSION_TTL_SECONDS` — browser session lifetime in seconds
47
+
34
48
Optional web runtime variables:
35
49
36
50
-`VITE_INVOLUTE_GRAPHQL_URL` — override the web app GraphQL endpoint (default: `http://localhost:4200/graphql`)
37
-
-`VITE_INVOLUTE_AUTH_TOKEN` — provide the web app bearer token at build/dev time
51
+
-`VITE_INVOLUTE_AUTH_TOKEN` — trusted local/dev bearer token for bypassing browser login
38
52
-`VITE_INVOLUTE_VIEWER_ASSERTION` — signed viewer assertion to act as a specific user without exposing the server secret
39
53
40
54
## Quick start
@@ -54,6 +68,8 @@ curl http://localhost:4201
54
68
55
69
Then open `http://localhost:4201` in your browser.
56
70
71
+
If Google OAuth is configured, the web nav will expose `Sign in with Google` and use session cookies. If it is not configured, the browser can still talk to the API with `VITE_INVOLUTE_AUTH_TOKEN` for trusted local development.
0 commit comments