---
title: Step 2. Configure connection properties
description: Explains how to install dependencies and configure the connection properties in the sample app for the React Native OIDC sign-on module tutorial with PingOne.
component: orchsdks
page_id: orchsdks:oidc:try-it-out/react-native/pingone/02_configuring-sample-for-pingone
canonical_url: https://developer.pingidentity.com/orchsdks/oidc/try-it-out/react-native/pingone/02_configuring-sample-for-pingone.html
llms_txt: https://developer.pingidentity.com/orchsdks/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
keywords: ["OAuth 2.0", "OpenID Connect", "Tutorial", "Source Code", "Integration", "SDK", "React Native", "PingOne", "connection properties"]
section_ids:
  installing_dependencies: Installing dependencies
  configuring_connection_properties: Configuring connection properties
---

# Step 2. Configure connection properties

[icon: circle-check, set=far]PingOne [icon: react, set=fab]React Native

* [Prepare](00_before-you-begin.html)

* [Download](01_download-sample-repo.html)

* **Configure**

* [Run](03_running-sample-pingone.html)

In this step, you install the project dependencies and configure the reactnative-oidc sample to connect to the OAuth 2.0 application you created in PingOne.

|   |                                                                                                                              |
| - | ---------------------------------------------------------------------------------------------------------------------------- |
|   | Run all the commands on this page from the sample app's project root folder, `sdk-sample-apps/reactnative/reactnative-oidc`. |

## Installing dependencies

1. Install the JavaScript dependencies:

   ```shell
   yarn install
   ```

2. iOS only, install the native CocoaPods dependencies:

   ```shell
   cd ios
   bundle install
   bundle exec pod install
   cd ..
   ```

3. On Android only, configure a keystore and add the passwords as follows:

   1. Generate a debug signing keystore:

      ```shell
      keytool -genkeypair -v \
        -keystore android/app/debug.keystore \
        -alias androiddebugkey \
        -keyalg RSA -keysize 2048 -validity 10000 \
        -storepass 5tr0ngP@S5w0rd! -keypass 5tr0ngP@S5w0rd! \
        -dname "CN=Android Debug,O=Android,C=US"
      ```

      Replace ***5tr0ngP\@S5w0rd!*** with a password of your choice, using the same value for both the `-storepass` and `-keypass` parameters.

      |   |                                                                                                                                                                                                                                                                                                                        |
      | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
      |   | The generated keystore file must be located in `sdk-sample-apps/reactnative/reactnative-oidc/android/app/debug.keystore`, and use the alias `androiddebugkey`.The build will fail if the keystore file is missing, or if the passwords in your Gradle properties do not match those used when generating the keystore. |

   2. Add the keystore credentials to your global Gradle properties file, for example at `~/.gradle/gradle.properties`:

      ```properties
      KEYSTORE_PASSWORD=5tr0ngP@S5w0rd!
      KEY_PASSWORD=5tr0ngP@S5w0rd!
      ```

## Configuring connection properties

1. Copy the example environment file:

   ```shell
   cp .env.example .env
   ```

2. Open `.env` in a text editor and update the `PINGONE_` values to match your environment:

   Example values in the .env file

   ```shell
   PINGONE_CLIENT_ID=6c7eb89a-66e9-ab12-cd34-eeaf795650b2
   PINGONE_DISCOVERY_ENDPOINT=https://auth.pingone.com/3072206d-c6ce-ch15-m0nd-f87e972c7cc3/as/.well-known/openid-configuration
   PINGONE_REDIRECT_URI=org.forgerock.oidc://oauth2redirect
   PINGONE_SCOPES=openid, email, address, profile
   PINGONE_ACR_VALUES=
   ```

   * *PINGONE\_CLIENT\_ID*

     The client ID from your OAuth 2.0 application in PingOne.

     For example, `6c7eb89a-66e9-ab12-cd34-eeaf795650b2`

     |   |                                                                                                                                                    |
     | - | -------------------------------------------------------------------------------------------------------------------------------------------------- |
     |   | You must specify the client ID value, such as `6c7eb89a-66e9-ab12-cd34-eeaf795650b2`.Do not enter the application name, such as `sdkNativeClient`. |

   * *PINGONE\_DISCOVERY\_ENDPOINT*

     The `.well-known` endpoint from your PingOne tenant.

     > **Collapse: How do I find my PingOne .well-known URL?**
     >
     > To find the `.well-known` endpoint for an OAuth 2.0 client in PingOne:
     >
     > 1. Log in to your PingOne administration console.
     >
     > 2. Go to **Applications > Applications**, and then select your OAuth 2.0 client.
     >
     >    For example, sdkPublicClient.
     >
     > 3. On the **Overview** tab, expand the **Connection Details** section, and then copy the **OIDC Discovery Endpoint** value.
     >
     >    ![Locating the .well-known URL in a PingOne client profile.](../../../../_images/p1-client-well-known.png)

   * *PINGONE\_REDIRECT\_URI*

     The redirect URI configured in your OAuth 2.0 client profile.

     This value must exactly match a redirect URI registered in your server.

     For this tutorial, the sample application is pre-configured to use the following redirect URI: `org.forgerock.oidc://oauth2redirect`.

     |   |                                                                                                                                                                                                                                                                                                                                                                                                      |
     | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
     |   | If you use a different redirect scheme, you must also update the values in the following locations:- Android - `manifestPlaceholders["appRedirectUriScheme"]` in `sdk-sample-apps/reactnative/reactnative-oidc/android/app/build.gradle`

     - iOS - `CFBundleURLSchemes` in `sdk-sample-apps/reactnative/reactnative-oidc/ios/PingSampleApp/Info.plist`

     - The OAuth 2.0 client settings in the server |

   * *PINGONE\_SCOPES*

     A comma-separated list of OAuth 2.0 scopes to request.

     For example, `openid, email, address, profile`

   * *PINGONE\_ACR\_VALUES*

     Optionally, specify which of the configured policies PingOne uses to authenticate users.

     Enter either a single DaVinci flow policy ID, or one or more PingOne policy names, separated by spaces.

     Leave this value empty to use the environment's default authentication policy.

3. Save your changes.

With the environment file configured, the React Native app will pick up your settings the next time you build and run it.