You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It still works, the project runs, but I would like to understand what might be happening here.
I am not able to reproduce this on my local machine using the same M2M profile.
Maybe you can point me in the right direction?
The logs are regarding token exchange. Currently we try to exchange external Idp tokens for internal Databricks tokens and silently fail if it is not possible
Closing as a duplicate of #904, which traces this warning to the token-exchange code raising KeyError('access_token') when the exchange endpoint returns an error, which is why the log line shows only 'access_token'. PR #928 addresses it there.
Activity
msrathore-db commentedon Nov 3, 2025
The logs are regarding token exchange. Currently we try to exchange external Idp tokens for internal Databricks tokens and silently fail if it is not possible
MCESARI-VA commentedon Nov 21, 2025
hello, is there any news on this "silently fail" ?
calbert82uhah commentedon Dec 17, 2025
I get the same error message when I run
(...)
entra_tokenis a valid Entra Id token.The connection works afterwards, but I do not understand why I get this warning on the console.
lorogno commentedon Aug 7, 2026
Still relevant!
vuanhphung commentedon Oct 30, 2026
Closing as a duplicate of #904, which traces this warning to the token-exchange code raising
KeyError('access_token')when the exchange endpoint returns an error, which is why the log line shows only'access_token'. PR #928 addresses it there._exchange_tokenraises KeyError('access_token') on error responses, discarding the real failure reason #904