Usage of ODBC driver with OIDC authentication

1. Select OIDC as the authentication mode

Provide the following details:

• Client ID
• Tenant ID
• Client Secret
• Authentication Timeout (Optional): Specifies the maximum time (in minutes) allowed for the user to complete the OIDC authentication process.
  • Default: 3 minutes
  • Valid Range: 1 to 9 minutes
  • If the user does not authenticate within this time, the process will time out and fail.

2. Add redirect URI to Azure Identity Provider (IdP)

Ensure the following redirect URI is added to your Azure IdP configuration:

http://localhost:8888/callback

This URI must be registered in the Azure IdP to enable successful redirection during authentication. For more information, see Configure redirect URI on Azure IdP.

3. Retrieving NZREST endpoint information for Netezza Performance Server

To locate the NZREST API endpoint, follow these steps:

1. Log in to your IBM Cloud account.
2. From the IBM Cloud console, go to the Resource List.
3. Under Services and Software, select Databases.
4. Click on your Netezza Performance Server instance to open its Service Instance Details page.
5. Scroll down to the Public Endpoints section.
6. Locate the API Server information listed there.

4. Set the NZREST environment variable

1. Open the System Properties window by clicking Edit the system environment variables from the Start menu or search bar.
2. In the System Properties window, click the Environment Variables button.
3. Under User variables, click New to create a new variable:

   Variable name: NZREST
   Variable value: <NZREST public endpoint>
   

   To edit this variable later, select it and click Edit.
4. Click Ok to save the changes.

1. Initiate the token request

• Click the Get Token button, after entering the required parameters in the ODBC driver. This action will launch your default web browser and open the authorization URL.

2. Authenticate via browser

Authenticate using the browser window that opens. Once authentication is successful:

• The token is returned to the ODBC driver.
• The Password field is automatically populated with the retrieved token.

The ODBC UI will remain unresponsive until authentication either succeeds or times out. Even if the browser is closed or authentication fails, the UI will stay frozen until the timeout period ends.

3. Register the OIDC user in Netezza

Ensure that the user account used for browser-based authentication is registered in Netezza with external OIDC authentication enabled.

You can register the OIDC user using either of the following methods:

• Configure Azure OIDC authentication using the Netezza UI
• Configure Azure OIDC authentication using the command-line

4. Test the connection

Click Test Connection in the driver to verify connectivity to NPS. Once the connection is successful, the same DSN can be reused to integrate Netezza with other tools.

After successful OIDC authentication, the user receives a 24-hour password. This password is automatically filled in the driver, enabling direct connection to Netezza. This feature supports Single Sign-On (SSO).