cancel
Showing results forย 
Search instead forย 
Did you mean:ย 
Data Engineering
Join discussions on data engineering best practices, architectures, and optimization strategies within the Databricks Community. Exchange insights and solutions with fellow data engineers.
cancel
Showing results forย 
Search instead forย 
Did you mean:ย 

Error: oidc: fetch .well-known: Get "https://%E2%80%93host/oidc/.well-known/oauth-authorization-serv

feliximmanuel
New Contributor II

I'm trying to authenticate databricks using WSL but suddenly getting this error.

/databricks-asset-bundle$ databricks auth login โ€“host https://<XXXXXXXXX>.12.azuredatabricks.net
Databricks Profile Name:<XXXXXXXXX>

Error: oidc: fetch .well-known: Get "https://%E2%80%93host/oidc/.well-known/oauth-authorization-server": dial tcp: lookup xn--host-z86a on 192.168.240.1:53: no such host

Someone could you please help me!

Thanks

1 REPLY 1

code-vj
New Contributor

It looks like the issue is caused by the dash before host. The command is using an en-dash (โ€“) instead of a regular hyphen (-) โ€” which breaks the URL parsing.

Try running this instead:

databricks auth login --host https://<your-instance>.azuredatabricks.net

(make sure you use two regular hyphens before host)

If youโ€™re testing your OIDC setup or want to validate .well-known endpoints, token responses, or redirect flows, you can use these tools:

These can help ensure your OIDC configuration and endpoints are working as expected.