Server configuration that includes well-known OIDC endpoint discovery.

When wellknown is provided, the client will fetch the OIDC discovery document to obtain endpoints like authorization, token, userinfo, etc.

Note: baseUrl is still required for AM-specific endpoints (authenticate, sessions) which are not part of the standard OIDC well-known response.

interface WellknownServerConfig {
    baseUrl: string;
    paths?: CustomPathConfig;
    timeout?: number;
    wellknown: string;
}

Properties

baseUrl: string

Base URL for AM-specific endpoints (authenticate, sessions)

paths?: CustomPathConfig

Custom path overrides for endpoints

timeout?: number

Request timeout in milliseconds

wellknown: string

URL to the OIDC well-known configuration endpoint