![]() |
VOOZH | about |
You can use the SQL Gateway from the ODBC Driver for Okta to query Okta data through a MySQL interface. Follow the procedure below to start the MySQL remoting service of the SQL Gateway and start querying using Node.js.
If you have not already done so, provide values for the required connection properties in the data source name (DSN). You can use the built-in Microsoft ODBC Data Source Administrator to configure the DSN. This is also the last step of the driver installation. See the "Getting Started" chapter in the help documentation for a guide to using the Microsoft ODBC Data Source Administrator to create and configure a DSN.
To connect to Okta, set the Domain connection string property to your Okta domain.
You will use OAuth to authenticate with Okta, so you need to create a custom OAuth application.
From your Okta account:
See the SQL Gateway Overview to set up connectivity to Okta data as a virtual MySQL database. You will configure a MySQL remoting service that listens for MySQL requests from clients. The service can be configured in the SQL Gateway UI.
👁 Creating a MySQL Remoting Service in SQL Gateway (Salesforce is shown)
The following example shows how to define a connection and execute queries to Okta with the mysql module. You will need the following information:
Connect to Okta data and start executing queries with the code below:
var mysql = require('mysql');
var connection = mysql.createConnection({
host : 'localhost',
database : 'CData Okta Sys',
port : '3306',
user : 'mysql_user',
password : 'test'
});
connection.connect();
connection.query('SELECT * FROM Users', function(err, rows, fields) {
if (err) throw err;
console.log(rows);
});
connection.end();
Download a free trial of the Okta ODBC Driver to get started:
Download NowLearn more:
👁 Okta IconThe Okta ODBC Driver is a powerful tool that allows you to connect with live data from Okta, directly from any applications that support ODBC connectivity.
Access Okta data like you would a database - read, write, and update Okta 0, etc. through a standard ODBC Driver interface.