Josep Piguillem
cbaad17fc7
Pireon OAuth clients allow a single grant type. With one PIREON_CLIENT_ID of type password, email + password worked but "Sign in with Pireon" failed with `unauthorized_client`. - PIREON_CLIENT_ID/SECRET: authorization_code client (Sign in with Pireon, Swagger UI). New PIREON_PASSWORD_CLIENT_ID/SECRET: password client, falling back to the former so existing setups keep working. - Refresh tries both clients: a refresh token only works with its issuer. - PIREON_PASSWORD_GRANT=false now also rejects password grants in the API (before it only hid the form). - /api/auth/config returns clientId: null when there is no authorization_code client, and the web hides "Sign in with Pireon". - docker-compose passes the new variables; docs 05/07, .env.example, openapi.json; unit tests for the client selection. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
23 lines
794 B
TypeScript
23 lines
794 B
TypeScript
export interface PireonConfig {
|
|
/** e.g. https://oauth.pireon.dev */
|
|
baseUrl: string;
|
|
/** Seconds a resolved token is trusted before asking Pireon again. */
|
|
sessionTtlSeconds: number;
|
|
requestTimeoutMs: number;
|
|
/**
|
|
* Pireon OAuth client with grant type `authorization_code` ("Sign in with
|
|
* Pireon", Swagger UI). Pireon clients allow a single grant type, so email +
|
|
* password uses its own client below.
|
|
*/
|
|
clientId?: string;
|
|
/** Kept server-side: browsers sign in through /api/auth/token. */
|
|
clientSecret?: string;
|
|
/** Pireon OAuth client with grant type `password`; defaults to the one above. */
|
|
passwordClientId?: string;
|
|
passwordClientSecret?: string;
|
|
scopes: string[];
|
|
passwordGrant: boolean;
|
|
}
|
|
|
|
export const PIREON_CONFIG = Symbol('PIREON_CONFIG');
|