topic Re: Error com.databricks.common.client.DatabricksServiceHttpClientException 403 Invalid access token in Data Engineering

Error com.databricks.common.client.DatabricksServiceHttpClientException 403 Invalid access token

skanapuram — Thu, 26 Dec 2024 15:14:48 GMT

I got this error "com.databricks.common.client.DatabricksServiceHttpClientException: 403: Invalid access token" during the run of a workflow job. It has been working for a while without error. Nothing has changed in regards to code or cluster. And it's working fine after starting the job again with no change.

Do you know what causes it?

Thank you!

Re: Error com.databricks.common.client.DatabricksServiceHttpClientException 403 Invalid access token

Alberto_Umana — Thu, 26 Dec 2024 16:41:32 GMT

Hi @skanapuram,

The error "com.databricks.common.client.DatabricksServiceHttpClientException: 403: Invalid access token" typically occurs when the access token used for authentication has expired or is invalid. Have you reviewed the driver logs of the job cluster? It might provide more details.

Also are you interacting with any type of token in your workflow?

Re: Error com.databricks.common.client.DatabricksServiceHttpClientException 403 Invalid access token

skanapuram — Thu, 26 Dec 2024 17:57:58 GMT

Thanks for the response,

From the driver logs, could see it has failed when it was running this below line
"DBUtilsHolder.dbutils.secrets.get"

Re: Error com.databricks.common.client.DatabricksServiceHttpClientException 403 Invalid access token

Alberto_Umana — Thu, 26 Dec 2024 21:23:06 GMT

Hi @skanapuram, was the secret renewed or change? You might want to validate if any token was rotated that might have caused the issue.

Re: Error com.databricks.common.client.DatabricksServiceHttpClientException 403 Invalid access token

john533 — Fri, 27 Dec 2024 06:22:51 GMT

When the access token used for authentication is invalid or has expired, the error "com.databricks.common.client.DatabricksServiceHttpClientException: 403: Invalid access token" usually appears. Have you looked at the task cluster's driver logs? It may give extra information.