Sudden Microsoft Identity error IDX20803

Question

Sudden Microsoft Identity error IDX20803

Alex D 16

Hello.

All of a sudden I am no longer able to log into my ASP.NET web api on localhost.

I've been getting this error:

    System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'https://login.windows.net/578XXXXXX/v2.0/.well-known/openid-configuration'.  
     ---> System.IO.IOException: IDX20804: Unable to retrieve document from: 'https://login.windows.net/578XXXXXX/v2.0/.well-known/openid-configuration'.  
     ---> System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 60 seconds elapsing.  
     ---> System.TimeoutException: A task was canceled.  
     ---> System.Threading.Tasks.TaskCanceledException: A task was canceled.  
       at ........

My configuration is correct:

  "AzureAd": {  
    "Instance": "https://login.windows.net",  
    "ClientId": "2103XXXXXXX",  
    "TenantId": "57XXXXXXX",  
    "Audience": "api://21XXXXX"  
  },

My code in Startup:

    builder.Services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)  
       .AddMicrosoftIdentityWebApi(builder.Configuration.GetSection("AzureAd"));

All this worked perfectly fine until today.

There are no problems in production. The same code works perfectly in the deployed Azure App.

Any ideas why I'm getting this time out issue? Could it be a network issue on my end?

Prasad, Raji 10 Reputation points

2023-03-13T05:32:23.6766667+00:00

Hi,

We are facing the same issue in our DEV and UAT environments. We have recently updated REDIs cache from 4.0 to 6.0 other than that no changes recently. Is there any solution for this?
Jacob Haapala 0 Reputation points

2023-06-20T08:54:41.73+00:00

Hello,

Did you figure out any solution to this issue?
Alex D 16 Reputation points

2023-06-20T09:04:46.56+00:00

@Jacob Haapala

Hello,

Not really, but I think it was a networking issue on my side.

I've reset my router and called my ISP for new credentials and that seemed to fix the issue, so it was strange.

6 answers

Your answer

Prasad, Raji 10 Reputation points

2023-03-13T05:32:23.6766667+00:00

Hi,

We are facing the same issue in our DEV and UAT environments. We have recently updated REDIs cache from 4.0 to 6.0 other than that no changes recently. Is there any solution for this?
Jacob Haapala 0 Reputation points

2023-06-20T08:54:41.73+00:00

Hello,

Did you figure out any solution to this issue?
Alex D 16 Reputation points

2023-06-20T09:04:46.56+00:00

@Jacob Haapala

Hello,

Not really, but I think it was a networking issue on my side.

I've reset my router and called my ISP for new credentials and that seemed to fix the issue, so it was strange.

Answer 1

Marilee Turscak-MSFT 37,411 Microsoft Employee Moderator

Hi @Alex D ,

Thanks for your post and sorry to hear that you are facing this issue! I understand that you are seeing the following error:

IDX20803: Unable to obtain configuration from: 'https://login.windows.net/578XXXXXX/v2.0/.well-known/openid-configuration'

If this has happened suddenly with no changes to your network, this might be related to a recent change in Azure that requires apps to use TLS 1.2. If you are still using deprecated TLS protocols and have not updated to TLS 1.2 and .NET framework 4.7 or later, you may face this error.

Otherwise if you have already updated the TLS version, this is normally a network error that is caused by the app being unable to connect to the Azure AD metadata endpoint. This occurs if something is blocking the connection (such as a firewall), the connection is not working for other reasons, or there is an outage (though I checked and did not find an outage report).

If you are using a proxy server or firewall, you also need to make sure that the URLs on this page are safelisted.

-

If the information helped you, please Accept the answer. This will help us and other community members as well.

Alex D 16 Reputation points

2022-12-10T10:03:08.587+00:00

Hi.

I've increased the timeout and it worked eventually, but took about 2 minutes just to get the OAuth config (compared to a few seconds before).

If I use Postman to request the tokens, it works fine and fast.

Just the ASP.NET apps seem to have issues.

I have TLS 1.2 enabled, no proxy running and Azure URLs are not blocked by firewall or antiviruses.

Any thoughts?

Niraj Jain 10

@Marilee Turscak-MSFT

I am also getting same error when running my .NET 6 API locally, it works fine when running URL of app service where same code has been deployed

 Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler[3]
      Exception occurred while processing message.
      System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'https://login.microsoftonline.com/<tenantId>/.well-known/openid-configuration'. Will retry at '7/19/2023 5:12:22 PM +00:00'. Exception: 'System.IO.IOException: IDX20804: Unable to retrieve document from: '[PII of type 'System.String' is hidden. For more details, see https://aka.ms/IdentityModel/PII.]'.

In my Windows 10 machine, I have TLS 1.2 enabled and there is no firewall or VPN used.

Answer 2

Karol Grodzicki 15

We had the same issue in .NET 7 application. It was fixed by updating Microsoft.Identity.Web package to 2.12.4 (previously was 2.5.0)

Socorro Beatriz Gonzalez Estrella 0 Reputation points

2024-06-24T19:27:08.88+00:00

Muchas gracias, su comentario fue de muchísima utilidad en mi proyecto, lo complementamos actualizando la versión de Azure.Identity

Answer 3

Hello,

We got the same issue in environments (DEV and Production) on my side.

So do we have any solution for this?

IDX20803: Unable to obtain configuration from: 'https://login.microsoftonline.com/common/discovery/instance?authorization_endpoint=https://login.microsoftonline.com/common/oauth2/v2.0/authorize&api-version=1.1'. IDX20804: Unable to retrieve document from: 'https://login.microsoftonline.com/common/discovery/instance?authorization_endpoint=https://login.microsoftonline.com/common/oauth2/v2.0/authorize&api-version=1.1'. An error occurred while sending the request. Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.. An existing connection was forcibly closed by the remote host.

Answer 4

Prasad, Raji 10

The app was referencing an expired SSL certificate from the server (VM in azure) and when we removed the expired certificate the issue got resolved.

0 comments

Answer 5

Ryan Brown 45

I have the same issue sometimes. Rebooting always works. So today I just tried turning off my wifi and reconnecting and that also fixed it.

Weird.

Carlos Saavedra 0 Reputation points

2026-09-15T18:17:57.9933333+00:00

I've been facing this weird issue from last week and somehow, turning off and on my WIFI seemed to do the trick. Thanks for that.
Were you able to spot what the main issue was? and why this happens?