Step 3. Configure connection properties

In this step, you configure the sample app to connect to the OAuth 2.0 application you created in PingFederate.

In the IDE of your choice, open the sdk-sample-apps folder you cloned in the previous step.
Open the /javascript/central-login-oidc/src/main.js file.
Locate the forgerock.Config.setAsync() method and update the properties to match your PingFederate environment:
```
await forgerock.Config.setAsync({
  clientId: process.env.WEB_OAUTH_CLIENT, // e.g. 'ForgeRockSDKClient' or PingOne Services Client GUID
  redirectUri: `${window.location.origin}`, // Redirect back to your app, e.g. 'https://localhost:8443' or the domain your app is served.
  scope: process.env.SCOPE, // e.g. 'openid profile email address phone revoke' When using PingOne services revoke scope is required
  serverConfig: {
    wellknown: process.env.WELL_KNOWN,
    timeout: process.env.TIMEOUT, // Any value between 3000 to 5000 is good, this impacts the redirect time to login. Change that according to your needs.
  },
});
```
Replace the following strings with the values you obtained when you registered an OAuth 2.0 application in PingFederate.
process.env.WEB_OAUTH_CLIENT

The client ID from your OAuth 2.0 application in PingFederate.

For example, sdkPublicClient

process.env.SCOPE

The scopes you added to your OAuth 2.0 application in PingFederate.

For example, openid profile email phone

process.env.WELL_KNOWN

The .well-known endpoint from your OAuth 2.0 application in PingFederate.

How do I form my PingFederate .well-known URL?

To form the .well-known endpoint for a PingFederate server:

Log in to your PingFederate administration console.

Navigate to System Server Protocol Settings.

Make a note of the Base URL value.

For example, https://pingfed.example.com

Do not use the admin console URL.

Append /.well-known/openid-configuration after the base URL value to form the .well-known endpoint of your server.

For example, https://pingfed.example.com/.well-known/openid-configuration.

The SDK reads the OAuth 2.0 paths it requires from this endpoint.

For example, https://pingfed.example.com/.well-known/openid-configuration

process.env.TIMEOUT

Enter how many milliseconds to wait before timing out the OAuth 2.0 flow.

For example, 3000
The result resembles the following:
```
await forgerock.Config.setAsync({
  clientId: "sdkPublicClient",
  redirectUri: `${window.location.origin}`,
  scope: "openid profile email phone",
  serverConfig: {
    wellknown: "https://auth.pingone.com/3072206d-c6ce-ch15-m0nd-f87e972c7cc3/as/.well-known/openid-configuration",
    timeout: 3000
  },
});
```

Ping SDKs

Step 3. Configure connection properties