Configuring the DaVinci module
PingOne JavaScript
Configure DaVinci module for JavaScript properties to connect to PingOne and step through an associated DaVinci flow.
The following shows a full DaVinci module configuration:
import { davinci } from '@forgerock/davinci-client';
const davinciClient = await davinci({
logger: {
level: 'warn',
custom: customLogger,
},
config: {
clientId: '6c7eb89a-66e9-ab12-cd34-eeaf795650b2',
serverConfig: {
wellknown: 'https://auth.pingone.com/3072206d-c6ce-ch15-m0nd-f87e972c7cc3/as/.well-known/openid-configuration',
timeout: 3000,
},
scope: '"openid", "email", "address", "profile", "phone"',
responseType: 'code',
},
});
The following properties are available for configuring the DaVinci module for JavaScript:
| Property | Description | Required? |
|---|---|---|
|
An interface for configuring how the SDK contacts the PingAM instance. Contains |
Yes |
|
Your PingOne server’s Example:
|
Yes |
|
A timeout, in milliseconds, for each request that communicates with your server. For example, for 30 seconds specify Defaults to |
No |
|
The For example, |
Yes |
|
A list of scopes to request when performing an OAuth 2.0 authorization flow, separated by spaces. For example, |
No |
|
The type of OAuth 2.0 flow to use, either Defaults to |
No |
| Property | Description | Required? |
|---|---|---|
|
Specify what level of logging the Orchestration SDK should output. Select one of the following:
Learn more in Configuring JavaScript logging. |
No |
|
Specify a custom logger the Orchestration SDK should use to output messages. Learn more in Customizing JavaScript logging. Example:
|
No |