Log contains null values when using OAuth to connect to Snowflake

Applies to

• Liquibase Secure (Pro)
• Liquibase Community (Open Source)

Conditions

• Snowflake
• Liquibase version 4.31 or older

Issue Summary

When connecting to Snowflake using OAuth tokens, the username in logs is replaced with the text string "null".

Error Message

An example of the error where the username is replaced. Note that the token is masked with asterisks and is expected behavior:

2 changesets have not been applied to null@jdbc:snowflake://******.aws.snowflakecomputing.com:321/

Root Cause

A bug caused the username value to be reported to logs incorrectly in Liquibase versions older than 4.32.

Resolution

Update Liquibase to v4.32.0+.

The latest releases can be found on Liquibase.com and GitHub.

Related Article(s)

Can Liquibase Connect to Snowflake using an OAuth token

Best Practices: Liquibase with Snowflake