Hi,

It occurs as you have two different authentication methods configured simultaneously.

1. PAT (Personal Access Token) - configured DATABRICKS_TOKEN environment variable
2. GitHub OIDC - configured DATABRICKS_TOKEN_AUDIENCE environment variable

You can remove one of these authentication methods from the environment variables. PAT authentication is simpler and you can use it.

Use PAT - Find and delete the DATABRICKS_TOKEN_AUDIENCE variable from either User variables (for your account only), or System variables (if set there). Keep these variables - DATABRICKS_HOST, DATABRICKS_TOKEN, DATABRICKS_WORKSPACE_ID, DATABRICKS_ACCOUNT_ID

Close and reopen any command prompt/terminal windows for changes to take effect. Retry the Lakebridge installation

Use GitHub OIDC

If you want to use GitHub OIDC authentication, remove DATABRICKS_TOKEN instead, but this requires additional GitHub Actions setup and is typically used for CI/CD pipelines

Hi @balajij8 ,

I am not able to find out DATABRICKS_TOKEN_AUDIENCE set in environment variable neither as user nor as system variable. Is there any other way I can find out this value and remove it so that only PAT authentication comes into picture when installing the Lakebridge? Thanks for your help

Hi @Himanshu_Singh 

When the process initializes it evaluates all available credentials across the system (environment variables, .databrickscfg file, CLI profiles). If it detects overlapping methods as in this case, traces of an OIDC configuration (DATABRICKS_TOKEN_AUDIENCE) alongside a Personal Access Token (DATABRICKS_TOKEN or pat) -it throws a ValueError to prevent ambiguous or insecure workspace connections. It is likely cached in the active terminal session retained by a background process.

You can follow below

• If the variables are cached in the current terminal session - Identify the variables in the active environment. Open a PowerShell terminal and list the active variables

# List DATABRICKS_* environment variables
Get-ChildItem Env: | Where-Object { $_.Name -like "DATABRICKS_*" } | Format-Table Name, Value​

• In the same PowerShell window (run as Administrator for system variables) execute

# Remove OIDC-related variables from User scope
[System.Environment]::SetEnvironmentVariable('DATABRICKS_TOKEN_AUDIENCE', $null, 'User')

# Remove from System scope (requires Administrator)
[System.Environment]::SetEnvironmentVariable('DATABRICKS_TOKEN_AUDIENCE', $null, 'Machine')

# If DATABRICKS_TOKEN is set via environment variable, remove it too
[System.Environment]::SetEnvironmentVariable('DATABRICKS_TOKEN', $null, 'User')
[System.Environment]::SetEnvironmentVariable('DATABRICKS_TOKEN', $null, 'Machine')

If you want the most stable and direct step - Remove the environment variables for credential management and rely exclusively on a configuration file. This provides a cleaner separation of environments. Create or edit your C:\Users\himan\.databrickscfg file to explicitly define your [DEFAULT] profile

[DEFAULT]
host = https://adb-7405615889085100.0.azuredatabricks.net
token = put the token

Retry the lakebridge installation after you remove the variables. You must close & reopen all terminals after removing the environment variables. Use the databrickscfg for authentication steps. Ensure the token is copied completely and the user account has necessary permissions. Regenerate the token if necessary.

More details here

Hi Himan, Run the 1 command below before you retry the lakebridge installation.

set DATABRICKS_AUTH_TYPE=pat

 Lakebridge will install without issues.