Configuration options for the journey client
Server configuration with required wellknown URL
Optionallogger?: { custom?: CustomLogger; level: LogLevel }Optional logger configuration
OptionalrequestMiddleware?: RequestMiddleware[]Optional middleware for request customization
A journey client instance, or a GenericError if configuration fails
// Basic usage - baseUrl and realmPath are inferred from wellknown
const client = await journey({
config: {
serverConfig: {
wellknown: 'https://am.example.com/am/oauth2/alpha/.well-known/openid-configuration',
},
},
});
// With explicit realmPath (when inference isn't desired)
const client = await journey({
config: {
serverConfig: {
wellknown: 'https://am.example.com/am/oauth2/alpha/.well-known/openid-configuration',
},
realmPath: 'alpha',
},
});
Creates a journey client for AM authentication tree/journey interactions.
Journey-client is designed specifically for ForgeRock Access Management (AM) servers. It uses AM-proprietary endpoints for callback-based authentication trees.