N/A | N/A | N/A | Add a bootstrapped ‘Synapse Command Line’ OAuth client. We use a new client and not client 0 for two reasons If we add OAuth flows to command line apps, a user should see a prompt for authorizing ‘Synapse Command Line’, which they wouldn’t see for client 0 There is a limit on active refresh tokens per user-client combination. If we decide to use client 0 to issue refresh tokens elsewhere (e.g. for browser sessions), then they could interfere/invalidate command line sessions.
| ❌ |
POST /oauth2/userGeneratedToken | OIDCTokenGenerationRequest { clientId: string
scope: Array<OAuthScope>
claims: OIDCClaimsRequest
} | OIDCTokenResponse | Generates a token response that users can copy and paste into the command line client. Effectively replaces API keys. In most cases, the clientId will be set to the ID used for the bootstrapped command line client (SWC could even hard-code it, since users likely only need to generate tokens for this client). | ✅ |
