---
title: Configuring the DaVinci module
description: Explains how to configure the DaVinci module for Android by setting properties to connect to PingOne and step through a DaVinci flow.
component: orchsdks
page_id: orchsdks:davinci:usage/android/02-configuring-the-davinci-module
canonical_url: https://developer.pingidentity.com/orchsdks/davinci/usage/android/02-configuring-the-davinci-module.html
revdate: Fri, 9 Jan 2026 17:23:51 +0000
keywords: ["DaVinci", "Android", "Configuration", "Properties", "PingOne", "Integration"]
---

# Configuring the DaVinci module

[icon: circle-check, set=far]PingOne [icon: android, set=fab]Android

* [Install](01-installing-the-davinci-module.html)

* **Configure**

* [Navigate](03-stepping-through-davinci-flows.html)

Configure DaVinci module for Android 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:

Configure DaVinci module connection properties

```kotlin
import com.pingidentity.davinci.DaVinci
import com.pingidentity.davinci.module.Oidc

val daVinci = DaVinci {
    logger = Logger.STANDARD
    module(Oidc) {
        clientId = "6c7eb89a-66e9-ab12-cd34-eeaf795650b2"
        discoveryEndpoint = "https://auth.pingone.com/3072206d-c6ce-ch15-m0nd-f87e972c7cc3/" +
            "as/.well-known/openid-configuration"
        scopes = mutableSetOf("openid", "profile", "email", "address", "revoke")
        redirectUri = "com.example.demo://oauth2redirect"
        additionalParameters = mapOf("customKey" to "customValue")
    }
}
```

The following properties are available for configuring the DaVinci module for Android:

**Properties**

| Property               | Description                                                                                                                                                                                                                                                                                                                                                                                              | Required? |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- |
| `discoveryEndpoint`    | Your PingOne server's `.well-known/openid-configuration` endpoint.*Example*:`https://auth.pingone.com/3072206d-c6ce-ch15-m0nd-f87e972c7cc3/as/.well-known/openid-configuration`                                                                                                                                                                                                                          | Yes       |
| `clientId`             | The `client_id` of the OAuth 2.0 client profile to use.For example, `6c7eb89a-66e9-ab12-cd34-eeaf795650b2`                                                                                                                                                                                                                                                                                               | Yes       |
| `scopes`               | A set of scopes to request when performing an OAuth 2.0 authorization flow\.For example, `"openid", "profile", "email", "address", "revoke"`.                                                                                                                                                                                                                                                            | Yes       |
| `redirectUri`          | The `redirect_uri` as configured in the OAuth 2.0 client profile.	This value must match a value configured in your OAuth 2.0 client.For example, `com.example.demo://oauth2redirect`.                                                                                                                                                                                                                    | Yes       |
| `timeout`              | A timeout, in seconds, for each request that communicates with the server.Default is `30` seconds.                                                                                                                                                                                                                                                                                                       | No        |
| `acrValues`            | 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:`"d1210a6b0b2665dbaa5b652221badba2"`                                                                                                                                                                                    | No        |
| `logger`               | Specify which logger the Orchestration SDK should use to output messages. Select from the built-in presets `STANDARD` (the default), `WARN`, or `NONE`.You can also create and use your own logger implementation. Learn more in [Customizing logging on Android](../../customization/logging/android-custom-logging.html).                                                                              | No        |
| `additionalParameters` | Add additional key-pair parameters as query strings to the initial OAuth 2.0 call to the `/authorize` endpoint.For example, `additionalParameters = mapOf("customKey" to "customValue")`&#xA;&#xA;You can access these additional OAuth 2.0 parameters in your DaVinci flows by using the authorizationRequest.\<customParameter> property.&#xA;&#xA;Learn more in Referencing PingOne data in the flow. | No        |