Rename /auth/restricted/ to auth/restricted/{iframe,oidc} for clarity and separation.

This commit is contained in:
Leo Vasanko
2026-02-15 03:05:11 +00:00
parent 701b0810bd
commit 8132189a04
7 changed files with 12 additions and 11 deletions
+3 -3
View File
@@ -53,7 +53,7 @@ oid_auth_codes: dict[str, OIDAuthCode] = {}
- `GET /auth/oidc/userinfo` — UserInfo endpoint (bearer token)
### Authorization (via existing restricted app)
- `GET /auth/restricted/?client_id=...&redirect_uri=...&response_type=code&scope=openid...`
- `GET /auth/restricted/oidc?client_id=...&redirect_uri=...&response_type=code&scope=openid...`
The restricted app detects OIDC params from URL and handles authentication via WebSocket.
@@ -83,9 +83,9 @@ The restricted app detects OIDC params from URL and handles authentication via W
## Authorization Flow
The `/auth/restricted/` page handles OIDC authorization alongside normal iframe auth:
The `/auth/restricted/oidc` page handles OIDC authorization (same code as `/auth/restricted/iframe` for API auth):
1. Client redirects to `/auth/restricted/?client_id=...&redirect_uri=...&response_type=code&scope=openid&state=...`
1. Client redirects to `/auth/restricted/oidc?client_id=...&redirect_uri=...&response_type=code&scope=openid&state=...`
2. Frontend detects OIDC params from `window.location.search`
3. Frontend passes raw query string to `/auth/ws/authenticate?{query_string}`
4. User authenticates via passkey