<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Error: oidc: fetch .well-known: Get &amp;quot;https://%E2%80%93host/oidc/.well-known/oauth-authorization-serv in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/error-oidc-fetch-well-known-get-quot-https-e2-80-93host-oidc/m-p/75927#M35102</link>
    <description>&lt;P&gt;I'm trying to authenticate databricks using WSL but suddenly getting this error.&lt;/P&gt;&lt;P&gt;/databricks-asset-bundle$ databricks auth login –host https://&amp;lt;XXXXXXXXX&amp;gt;.12.azuredatabricks.net&lt;BR /&gt;Databricks Profile Name:&amp;lt;XXXXXXXXX&amp;gt;&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;Someone could you please help me!&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Thu, 27 Jun 2024 09:14:22 GMT</pubDate>
    <dc:creator>feliximmanuel</dc:creator>
    <dc:date>2024-06-27T09:14:22Z</dc:date>
    <item>
      <title>Error: oidc: fetch .well-known: Get "https://%E2%80%93host/oidc/.well-known/oauth-authorization-serv</title>
      <link>https://community.databricks.com/t5/data-engineering/error-oidc-fetch-well-known-get-quot-https-e2-80-93host-oidc/m-p/75927#M35102</link>
      <description>&lt;P&gt;I'm trying to authenticate databricks using WSL but suddenly getting this error.&lt;/P&gt;&lt;P&gt;/databricks-asset-bundle$ databricks auth login –host https://&amp;lt;XXXXXXXXX&amp;gt;.12.azuredatabricks.net&lt;BR /&gt;Databricks Profile Name:&amp;lt;XXXXXXXXX&amp;gt;&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;Someone could you please help me!&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 27 Jun 2024 09:14:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/error-oidc-fetch-well-known-get-quot-https-e2-80-93host-oidc/m-p/75927#M35102</guid>
      <dc:creator>feliximmanuel</dc:creator>
      <dc:date>2024-06-27T09:14:22Z</dc:date>
    </item>
    <item>
      <title>Re: Error: oidc: fetch .well-known: Get "https://%E2%80%93host/oidc/.well-known/oauth-authoriza</title>
      <link>https://community.databricks.com/t5/data-engineering/error-oidc-fetch-well-known-get-quot-https-e2-80-93host-oidc/m-p/138385#M50920</link>
      <description>&lt;P&gt;It looks like the issue is caused by the dash before host. The command is using an &lt;STRONG&gt;en-dash (–)&lt;/STRONG&gt; instead of a &lt;STRONG&gt;regular hyphen (-)&lt;/STRONG&gt; — which breaks the URL parsing.&lt;/P&gt;&lt;P&gt;Try running this instead:&lt;/P&gt;&lt;LI-CODE lang="javascript"&gt;databricks auth login --host https://&amp;lt;your-instance&amp;gt;.azuredatabricks.net&lt;/LI-CODE&gt;&lt;P&gt;(make sure you use &lt;STRONG&gt;two regular hyphens&lt;/STRONG&gt; before host)&lt;/P&gt;&lt;P&gt;If you’re testing your OIDC setup or want to validate .well-known endpoints, token responses, or redirect flows, you can use these tools:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;&lt;A class="" href="https://ssojet.com/oidc-tester" target="_blank" rel="noopener"&gt;OIDC Debugger&lt;/A&gt; – test OIDC authorization code flow&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;A class="" href="https://ssojet.com/jwt-validator/" target="_blank" rel="noopener"&gt;JWT.io&lt;/A&gt; – inspect and verify JWT tokens&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;A href="https://ssojet.com/oidc-playground/" target="_blank" rel="noopener"&gt;OAuth Playground&lt;/A&gt;&amp;nbsp;&amp;nbsp;– simulate OIDC &amp;amp; OAuth flows&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;These can help ensure your OIDC configuration and endpoints are working as expected.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Nov 2025 09:28:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/error-oidc-fetch-well-known-get-quot-https-e2-80-93host-oidc/m-p/138385#M50920</guid>
      <dc:creator>code-vj</dc:creator>
      <dc:date>2025-11-10T09:28:38Z</dc:date>
    </item>
    <item>
      <title>Re: Error: oidc: fetch .well-known: Get "https://%E2%80%93host/oidc/.well-known/oauth-authoriza</title>
      <link>https://community.databricks.com/t5/data-engineering/error-oidc-fetch-well-known-get-quot-https-e2-80-93host-oidc/m-p/141361#M51707</link>
      <description>&lt;P&gt;Great, these are amazing resources! I'm using them to test my IAM apps and flow.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2025 05:36:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/error-oidc-fetch-well-known-get-quot-https-e2-80-93host-oidc/m-p/141361#M51707</guid>
      <dc:creator>guptadeepak</dc:creator>
      <dc:date>2025-12-08T05:36:28Z</dc:date>
    </item>
  </channel>
</rss>

