Skip to content
LogScale Self-Hosted
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

### PingOne

The integration process between PingOne, a global authentication authority, and LogScale enables secure user access through SAML, OAuth, and OpenID Connect standards. Step-by-step instructions detail the configuration of SP connections, browser SSO settings, attribute contracts, and metadata file generation within PingOne for successful LogScale integration.

PingOne serves as a global authentication authority that allows any user to access securely LogScale. It integrates with identity standards like SAML, OAuth, and OpenID Connect. See the Ping Identity Documentation for more information on PingOne.

#### Prerequisites to configure PingOne

Prior to configuring PingOne for authentication with LogScale make sure to have the following:

- PingOne account

#### Configure PingOne to integrate with LogScale

There are several steps to configure the PingOne for integration with LogScale.

To configure your PingOne account:

1. In the dashboard click Add Environment.

   Figure 62. Add environment to account

2. Select Customer Solution and click Next.

   Figure 63. Select Customer Solution

3. Click Next.

   Figure 64. Add environment to account

4. Name your deployment and click Next.

   Figure 65. Name the deployment

Your dashboard should appear similar to this:

Figure 66. PingOne account configured

Once you have created the environment, proceed with configuring the environment.

1. Click your environment you created. You should see a page similar to the following:

   Figure 67. Open the environment

2. Navigate to Connections and Applications and click the + (plus) icon.

   Figure 68. Navigate to create a connection

3. Enter a name in the Applications Name and select SAML Application. Click Configure.

   Figure 69. Create a connection

4. Click the radio button for Manually Enter and enter the ACS URL and Entity ID. Click Save.

   Figure 70. Enter ACS URL and Entity ID

5. Click Configuration. This is where you will find the SAML settings you will use later.

   Figure 71. Metadata created and download options

6. Click to download the Identity Provider Certificate and save this in a certs directory where your native app is running.

The last task in the PingOne dashboard is to add users.

1. In the PingOne dashboard click Identities then Users and Add User.

   Figure 72. Add users in the dashboard

2. In the pop-up that appears scroll down and enter the username as an email address and click Save.

   Figure 73. Enter username

3. Once the user is created, click Reset Password. This will allow you to set a password for the user to use at login.

   Figure 74. User created and reset password

Now you are ready to configure LogScale, using the metadata information and certificate you just exported.

#### Configure LogScale to use PingOne

When PingOne is configured to work with LogScale, you must configure LogScale to work with PingOne.

To configure PingOne to work with LogScale, you must set the configuration variables as described in Configure SAML for LogScale Self-Hosted.

#### Test the PingOne integration setup

Once all of the necessary steps to set up the PingOne authentication for LogScale are completed, you need to test the setup.

1. Go to a Terminal and start LogScale with the following command:

   shell

       ./run.sh

   Allow two to three minutes for LogScale to start.

2. Connect to localhost in a browser. It should redirect you to a PingOne login.

3. Sign in to your PingOne. You should be taken to LogScale.

#### Enter search term