--- title: Before you begin description: Outlines the prerequisites and server configuration steps required before starting the React Native OIDC sign-on module tutorial for PingOne. component: orchsdks page_id: orchsdks:oidc:try-it-out/react-native/pingone/00_before-you-begin canonical_url: https://developer.pingidentity.com/orchsdks/oidc/try-it-out/react-native/pingone/00_before-you-begin.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", "prerequisites"] section_ids: prerequisites: Prerequisites server_configuration: Server configuration --- # Before you begin [icon: circle-check, set=far]PingOne [icon: react, set=fab]React Native * **Prepare** * [Download](01_download-sample-repo.html) * [Configure](02_configuring-sample-for-pingone.html) * [Run](03_running-sample-pingone.html) To successfully complete this tutorial refer to the prerequisites in this section. The tutorial also requires a configured PingOne instance. ## Prerequisites * React Native This sample app requires React Native 0.80.1 or later. * iOS This sample app requires iOS 16.0 or later. * Android This sample app requires Android 10 (API level 29) or later. The React Native development environment must be fully configured before you begin. Follow the official [React Native environment setup guide](https://reactnative.dev/docs/set-up-your-environment) and ensure the following tools are installed: * Node.js and Yarn Install [Node.js](https://nodejs.org/) version 20 or later. This project uses Yarn. Install Yarn by running: ```shell corepack enable ``` * Xcode (iOS only) Download and install [Xcode](https://developer.apple.com/xcode/) from the Mac App Store. Xcode 15 or later is recommended. * Ruby and Bundler (iOS only) Ruby 3.3.6 or later is required to manage CocoaPods. | | | | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | | macOS ships with an older version of Ruby that is not compatible with this project.Install a current version using [rbenv](https://rbenv.org/) or a similar version manager before continuing. | Install [Bundler](https://bundler.io/) with: ```shell gem install bundler ``` * CocoaPods (iOS only) CocoaPods is installed locally during the tutorial. You do not need to install it globally. * Android Studio (Android only) Download and install [Android Studio](https://developer.android.com/studio). An Android emulator or physical device is required to run the app. To add a virtual device, refer to [Create and manage virtual devices](https://developer.android.com/studio/run/managing-avds) on the Android Developers website. * Java (Android only) Android Studio includes an embedded JDK. Java 17 is recommended and is bundled with recent versions of Android Studio. * `keytool` (Android only) `keytool` is part of the Java Development Kit (JDK) and is used to generate the debug signing keystore required for the Android build. It is included with Android Studio's bundled JDK. ## Server configuration This tutorial requires you to configure your PingOne server as follows: > **Collapse: Task 1. Create a demo user** > > The samples and tutorials in this documentation often require that you have an identity set up so that you can test authentication. > > To create a demo user in PingOne, follow these steps: > > 1. Log in to your PingOne administration console. > > 2. In the left panel, navigate to Directory > Users. > > 3. Next to the Users label, click the plus icon ([icon: plus, set=fa]). > > PingOne displays the Add User panel. > > 4. Enter the following details: > > * **Given Name** = `Demo` > > * **Family Name** = `User` > > * **Username** = `demo` > > * **Email** = `demo.user@example.com` > > * **Population** = `Default` > > * **Password** = `Ch4ng3it!` > > 5. Click Save. > **Collapse: Task 2. Register a public OAuth 2.0 client** > > To register a *public* OAuth 2.0 client application in PingOne for use with the Orchestration SDKs for Android and iOS, follow these steps: > > 1. Log in to your PingOne administration console. > > 2. In the left panel, navigate to Applications > Applications. > > 3. Next to the Applications label, click the plus icon ([icon: plus, set=fa]). > > PingOne displays the Add Application panel. > > 4. In Application Name, enter a name for the profile, for example `sdkNativeClient` > > 5. Select Native as the Application Type, and then click Save. > > 6. On the Configuration tab, click the pencil icon ([icon: pencil, set=fa]). > > 1. In Grant Type, select the following values: > > `Authorization Code` > > `Refresh Token` > > 2. In Redirect URIs, enter the following values: > > `org.forgerock.oidc://oauth2redirect` > > 3. In Token Endpoint Authentication Method, select `None`. > > 4. In the **Advanced Settings** section, enable **Terminate User Session by ID Token**. > > 5. Click Save. > > 7. On the Resources tab, next to Allowed Scopes, click the pencil icon ([icon: pencil, set=fa]). > > 1. In Scopes, select the following values: > > `email` > > `phone` > > `profile` > > | | | > | - | ------------------------------------------ | > | | The `openid` scope is selected by default. | > > The result resembles the following: > > ![Adding scopes to an application.](../../../../_images/pingone-oidc-native-scopes-en.png)Figure 1. Adding scopes to an application. > > 8. Optionally, on the Policies tab, click the pencil icon ([icon: pencil, set=fa]) to select the authentication policies for the application. > > | | | > | - | -------------------------------------------------------------------------------------------------------------------------------------- | > | | Applications that have no authentication policy assignments use the environment's default authentication policy to authenticate users. | > > If you have a DaVinci license, you can select PingOne policies or DaVinci Flow policies, but not both. If you do not have a DaVinci license, the page only displays PingOne policies. > > To use a *PingOne policy*: > > 1. Click [icon: plus, set=fa]Add policies and then select the policies that you want to apply to the application. > > 2. Click Save. > > PingOne applies the policies in the order in which they appear in the list. PingOne evaluates the first policy in the list first. If the requirements are not met, PingOne moves to the next one. > > For more information, see [Authentication policies for applications](https://docs.pingidentity.com/pingone/applications/p1_auth_policies_for_applications.html). > > To use a *DaVinci Flow policy*: > > 1. You must clear all PingOne policies. Click Deselect all PingOne Policies. > > 2. In the confirmation message, click Continue. > > 3. On the DaVinci Policies tab, select the policies that you want to apply to the application. > > 4. Click Save. > > PingOne applies the first policy in the list. > > 9. Click Save. > > 10. Enable the OAuth 2.0 client application by using the toggle next to its name: > > ![Enable the application using the toggle.](../../../../_images/pingone-apps-enable-native-client-en.png)Figure 2. Enable the application using the toggle. > > The application is now configured to accept client connections from and issue OAuth 2.0 tokens to the Android and iOS PingOne example applications and tutorials covered by this documentation.