Authentication methods

Data Integrity Suite

Product

Spatial_Analytics

Data_Integration

Data_Enrichment

Data_Governance

Precisely_Data_Integrity_Suite

geo_addressing_1

Data_Observability

Data_Quality

dis_core_foundation

Services

Spatial Analytics

Data Integration

Data Enrichment

Data Governance

Geo Addressing

Data Observability

Data Quality

Core Foundation

ft:title

Data Integrity Suite

ft:locale

en-US

PublicationType

pt_product_guide

copyrightfirst

2000

copyrightlast

2026

This section provides you the different authentication method used for Snowflake in Data Integrity Suite.

Choose the type of authorization from the drop-down menu. This determines how the system will authenticate your credentials.

Table 1. Authentication type
Field	Description
Authentication type	Password: Use this option if you prefer to authenticate using a password. Username: Specifies the user ID credentials for authorization when connecting to the database server. This is a mandatory field. Example: db_user Password: Specifies the password credentials corresponding to the username for authorization when connecting to the database server. This is a mandatory field. Example: password123
	Private Key (Unencrypted): Use this option if you prefer to authenticate using a private key that isn’t encrypted. Choose this only if you don’t need to protect the key with a password.. Username: Specifies the user ID credentials for authorization when connecting to the database server. This is a mandatory field. Example: db_user Private key: Specifies the private key corresponding to the username for authorization when connecting to the database server. This is a mandatory field. Example: \nMIIEvQIBADANBgkqhkiG9w0BAQEFAASC.
	Private Key (Encrypted): Use this option if you prefer to authenticate using a private key. Username: Specifies the user ID credentials for authorization when connecting to the database server. This is a mandatory field. Example: db_user Private key: Specifies the private key corresponding to the username for authorization when connecting to the database server. This is a mandatory field. Example: \nMIIEvQIBADANBgkqhkiG9w0BAQEFAASC. Passphrase: Specifies the password used to unlock the encrypted private key. Required when the private key is passphrase-protected. Example: MySecureKey123!

Generate an encrypted private key

This section describes the procedure to generate an encrypted RSA key pair using OpenSSL and configure the public key for a Snowflake user to enable key-pair authentication. The private key is generated in PKCS#8 format and encrypted using PBE-SHA1-3DES.

Open terminal and run the following command to generate a 2048-bit RSA private key in PKCS#8 format, encrypted using v1 PBE-SHA1-3DES.
openssl genrsa 2048 | openssl pkcs8 -topk8 -inform PEM -v1 PBE-SHA1-3DES -out <file_name>
Note: Ensure that the <file_name> is saved with a .p8 extension. Example:rsa_key_encrypted.p8
When this command is executed, OpenSSL prompts for an encryption password. This password is required to protect the private key and must be entered twice for confirmation. Upon successful execution, an encrypted private key file named rsa_key_encrypted.p8 is created. This file must be kept secure and should never be shared.
Set a password for the encrypted private key when prompted, and confirm it by entering the same password again at the verification prompt.
To extract the public key from the encrypted private key, use the following command:

openssl rsa -in <file_name> -pubout -out rsa_key_public.pub
During execution, OpenSSL prompts for the passphrase associated with the encrypted private key. After successful authentication, the corresponding public key is extracted and written to the file rsa_key_public.pub. This public key can be safely shared and used for authentication configuration.
After running the above command, you will have two files generated in the specified directory:
- rsa_key_encrypted.p8 (encrypted private key)
- rsa_key_public.pub (public key)
To associate the public key with a user in Snowflake, run the following command:

ALTER USER <your_username> SET RSA_PUBLIC_KEY='<base64_encoded_public_key>';