Write a Simple Go Application to work with PingOne Data on Linux

Go is an open source programming language that enables you to easily build software on Linux/UNIX machines. When Go is paired with the ODBC Driver for PingOne and unixODBC you are able write applications with connectivity to live PingOne data. This article will walk you through the process of installing the ODBC Driver for PingOne, configuring a connection using the unixODBC Driver Manager, and creating a simple Go application to work with PingOne data.

Using the CData ODBC Drivers on a Unix/Linux Machine

The CData ODBC Drivers are supported in various Red Hat-based and Debian-based systems, including Ubuntu, Debian, RHEL, CentOS, and Fedora. There are also several libraries and packages that are required, many of which may be installed by default, depending on your system. For more information on the supported versions of Linux operating systems and the required libraries, please refer to the "Getting Started" section in help documentation (installed and found online).

Installing the Driver Manager

Before installing the driver, you need to be sure that your system has a driver manager. For this article, you will use unixODBC, a free and open source ODBC driver manager that is widely supported.

For Debian-based systems like Ubuntu, you can install unixODBC with the APT package manager:

apt-get install unixodbc unixodbc-dev

For systems based on Red Hat Linux, you can install unixODBC with yum or dnf:

yum install unixODBC unixODBC-devel

The unixODBC driver manager reads information about drivers from an odbcinst.ini file and about data sources from an odbc.ini file. You can determine the location of the configuration files on your system by entering the following command into a terminal:

odbcinst -j

NOTE: You may need to install odbcinst. Use the following command in a terminal:

apt install odbcinst

The output of the command will display the locations of the configuration files for ODBC data sources and registered ODBC drivers. User data sources can only be accessed by the user account whose home folder the odbc.ini is located in. System data sources can be accessed by all users. Below is an example of the output of this command:

DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
FILE DATA SOURCES..: /etc/ODBCDataSources
USER DATA SOURCES..: /home/myuser/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8

Installing the Driver

You can download the driver in standard package formats: the Debian .deb package format or the .rpm file format. Once you have downloaded the file, you can install the driver from the terminal.

The driver installer registers the driver with unixODBC and creates a system DSN, which can be used later in any tools or applications that support ODBC connectivity.

For Debian-based systems like Ubuntu, run the following command with sudo or as root:

dpkg -i /path/to/package.deb

For systems that support .rpms, run the following command with sudo or as root:

rpm -i /path/to/package.rpm

Once the driver is installed, you can list the registered drivers and defined data sources using the unixODBC driver manager:

List the Registered Driver(s)

odbcinst -q -d
CData ODBC Driver for PingOne
...

List the Defined Data Source(s)

odbcinst -q -s
CData PingOne Source
...

To use the CData ODBC Driver for PingOne with unixODBC, you need to ensure that the driver is configured to use UTF-16. To do so, edit the INI file for the driver (cdata.odbc.pingone.ini), which can be found in the lib folder in the installation location (typically /opt/cdata/cdata-odbc-driver-for-pingone), as follows:

cdata.odbc.pingone.ini

...

[Driver]
DriverManagerEncoding = UTF-16

Modifying the DSN

When the driver is installed, a system DSN should be predefined. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties. Additionally, you can create user-specific DSNs that will not require root access to modify in $HOME/.odbc.ini.

To connect to PingOne, configure these properties:

• : The region where the data for your PingOne organization is being hosted.
• : The type of authentication to use when connecting to PingOne.
• Either (required when using the default PingOne domain) or , configured as described below.

Configuring WorkerAppEnvironmentId

is the ID of the PingOne environment in which your Worker application resides. This parameter is used only when the environment is using the default PingOne domain (auth.pingone). It is configured after you have created the custom OAuth application you will use to authenticate to PingOne, as described in Creating a Custom OAuth Application in the Help documentation.

First, find the value for this property:

1. From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
2. Find the environment in which you have created your custom OAuth/Worker application (usually Administrators), and click Manage Environment. The environment's home page displays.
3. In the environment's home page navigation sidebar, click Applications.
4. Find your OAuth or Worker application details in the list.
5. Copy the value in the Environment ID field. It should look similar to:
   

   WorkerAppEnvironmentId='11e96fc7-aa4d-4a60-8196-9acf91424eca'

Now set to the value of the Environment ID field.

Configuring AuthorizationServerURL

is the base URL of the PingOne authorization server for the environment where your application is located. This property is only used when you have set up a custom domain for the environment, as described in the PingOne platform API documentation. See Custom Domains.

Authenticating to PingOne with OAuth

PingOne supports both OAuth and OAuthClient authentication. In addition to performing the configuration steps described above, there are two more steps to complete to support OAuth or OAuthCliet authentication:

• Create and configure a custom OAuth application, as described in Creating a Custom OAuth Application in the Help documentation.
• To ensure that the driver can access the entities in Data Model, confirm that you have configured the correct roles for the admin user/worker application you will be using, as described in Administrator Roles in the Help documentation.
• Set the appropriate properties for the authscheme and authflow of your choice, as described in the following subsections.

OAuth (Authorization Code grant)

Set to OAuth.

Desktop Applications

Get and Refresh the OAuth Access Token

After setting the following, you are ready to connect:

• : GETANDREFRESH. To avoid the need to repeat the OAuth exchange and manually setting the each time you connect, use .
• : The Client ID you obtained when you created your custom OAuth application.
• : The Client Secret you obtained when you created your custom OAuth application.
• : The redirect URI you defined when you registered your custom OAuth application. For example: https://localhost:3333

When you connect, the driver opens PingOne's OAuth endpoint in your default browser. Log in and grant permissions to the application. The driver then completes the OAuth process:

1. The driver obtains an access token from PingOne and uses it to request data.
2. The OAuth values are saved in the location specified in , to be persisted across connections.

The driver refreshes the access token automatically when it expires.

For other OAuth methods, including Web Applications, Headless Machines, or Client Credentials Grant, refer to the Help documentation.

/etc/odbc.ini or $HOME/.odbc.ini

[CData PingOne Source]
Driver = /opt/cdata/cdata-odbc-driver-for-pingone/lib/libpingoneodbc.x64.so
Description = My Description
AuthScheme = OAuth
WorkerAppEnvironmentId = eebc33a8-xxxx-4f3a-yyyy-d3e5262fd49e
Region = NA
OAuthClientId = client_id
OAuthClientSecret = client_secret
InitiateOAuth = GETANDREFRESH

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Creating a Simple Go App for PingOne Data

With the Driver Manager installed and the DSN configured, you are ready to create a simple Go application to work with your PingOne data. To start, install a Go driver for ODBC databases. While there are several options available, this article will use the odbc driver found at https://github.com/alexbrainman/odbc.

Installing ODBC on Linux

There are a series of steps required to install the ODBC driver for Go.

1. Create the $HOME/golang/go path (if it does not exist) by entering the following commands in a terminal:

   mkdir /root/golang
   mkdir /root/golang/go
    

2. Define the GOPATH environment variable:

   export GOPATH=$HOME/golang/go
    

3. Create a module inside the new Go directory:

   cd $GOPATH
   go mod init myproject
    

4. Install the Go driver for ODBC databases:

   go get http://github.com/alexbrainman/odbc
    

Now you are ready to create and execute a simple Go application.

Sample Go Application

The sample application issues a simple SQL SELECT query for PingOne data and displays the results. Create the directory $GOPATH/src/cdata-odbc-pingone and create a new Go source file, copying the source code from below.

cdata-odbc-pingone.go

package main

import (
 _ "github.com/alexbrainman/odbc"
 "database/sql"
 "log"
 "fmt"
)

func main() {
 db, err := sql.Open("odbc",
 "DSN=CData PingOne Source")
 if err != nil {
 log.Fatal(err)
 }

 var (
 id string
 username string
 )

 rows, err := db.Query("SELECT Id, Username FROM [CData].[Administrators].Users WHERE EmployeeType = ?", "Contractor")
 if err != nil {
 log.Fatal(err)
 }
 defer rows.Close()
 for rows.Next() {
 err := rows.Scan(&id, &username)
 if err != nil {
 log.Fatal(err)
 }
 fmt.Println(id, username)
 }
 err = rows.Err()
 if err != nil {
 log.Fatal(err)
 }

 defer db.Close()
}

In the terminal, navigate to the Go application directory and build the application:

go build

After the application builds, you will be able to execute the application, displaying your PingOne data:

./cdata-odbc-pingone

At this point, you have a simple Go application for working with PingOne data. From here, you can easily expand the application, adding deeper read functionality through familiar SQL queries.