Configuring the DaVinci module
PingOne iOS
Configure DaVinci module for iOS properties to connect to PingOne and step through an associated DaVinci flow.
The following shows an example DaVinci module configuration, using the underlying Oidc module:
let daVinci = DaVinci.createDaVinci { config in
config.logger = LogManager.standard
// Oidc as module
config.module(OidcModule.config) { oidcValue in
oidcValue.clientId = "6c7eb89a-66e9-ab12-cd34-eeaf795650b2"
oidcValue.discoveryEndpoint = "https://auth.pingone.com/3072206d-c6ce-ch15-m0nd-f87e972c7cc3/as/.well-known/openid-configuration"
oidcValue.scopes = ["openid", "profile", "email", "address", "revoke"]
oidcValue.redirectUri = "com.example.demo://oauth2redirect"
oidcValue.additionalParameters = ["customKey":"customValue"]
}
}
The following properties are available for configuring the DaVinci module for iOS:
| Property | Description | Required? | ||
|---|---|---|---|---|
|
Your PingOne server’s Example:
|
Yes |
||
|
The For example, |
Yes |
||
|
A set of scopes to request when performing an OAuth 2.0 authorization flow. For example, |
Yes |
||
|
The
For example, |
Yes |
||
|
A timeout, in seconds, for each request that communicates with the server. Default is |
No |
||
|
Request which flow the PingOne server uses by adding an Authentication Context Class Reference (ACR) parameter. Enter a single DaVinci policy by using its flow policy ID. Example:
|
No |
||
|
Specify which logger the Orchestration SDK should use to output messages. Select from the built-in presets You can also create and use your own logger implementation. Learn more in Customizing logging on iOS. |
No |
||
|
Add additional key-pair parameters as query strings to the initial OAuth 2.0 call to the For example,
|
No |