Snowflake connector authentication failure in Adobe Experience Platform

Ensure the private key is formatted correctly with proper headers

--BEGIN PRIVATE KEY-- [ Key Content] --END PRIVATE KEY--
Alternatively, if using an encrypted private key:
  --BEGIN ENCRYPTED PRIVATE KEY-- [ Key Content] --END ENCRYPTED PRIVATE KEY--

Regenerate the private key using OpenSSL with the following command:

openssl genrsa 2048 | openssl pkcs8 -topk8 -v2 des3 -inform PEM -out rsa_key.p8.

Encode the regenerated key in Base64 format without trailing newline characters. (\n) Avoid sending keys via email or messaging platforms like Teams, as this can introduce formatting issues (for example, extra spaces).

Verify that the user account in Snowflake is tied to the corresponding public key. For steps, refer to How to: Verify the Public/Private Key Connectivity using SnowSQL and Key-pair authentication and key-pair rotation in the Snowflake community.

Confirm that the account name adheres to Snowflake’s naming conventions. For example, prepend your organization name to the account name (e.g.,  orgname-account_name). For more information, refer to Account Identifiers in Snowflake documentation.

Ensure all required IP ranges for AEP are whitelisted in your Snowflake environment. For more information, refer to IP address allowlist for source connectors.

To confirm whether AEP is attempting a connection, use an invalid private key intentionally and check if any login attempts appear in Snowflake’s login history.

Analyze logs generated during connection attempts for specific error codes or messages such as The request could not be processed  or Failed to parse PEM block.

If issues persist after performing these checks, escalate through Adobe supportwith detailed logs and request IDs.