Hello Mc Alex. If you inspect the launchSettings file of the Web API project, you will find registered both URIs: “applicationUrl”: “https://localhost:5001;http://localhost:5000“,

Please chack that and also that the Configure method (Startup class) contains this line: app.UseHttpsRedirection();

In your example where you have obtained the token and retrieve results successfully, the postman graphic shows you using https and port 5001. This doesn’t work for me (but it all works fine with http/port 5000). I went back into ConfigureServices, and set ‘opt.RequireHttpsMetadata = true’ in the addAuthentication(“Bearer”) section, but this didn’t make a difference. Should I be able to retrieve results (using a token) on https and port 5001?

I browser the link https://localhost:5005/.well-known/openid-configuration and it works well.

Please help me. Thanks

Hi. I would gladly help you but without your code it is not that simple. Please download our source code, you have a link at the top of this article, and compare your solution with ours. This is the easiest way to find what you missed.

I browser the link https://localhost:5005/.well-known/openid-configuration and it works well.

Please help me. Thanks

You are very welcome. Thank you too, for these kind words. This really means a lot to me. Once you are done with this series, if you want, you can check our main page and dive into the Angular or Blazor WASM course using IS4. Just to step out of the MVC client world 🙂

Well seems like http2 is what’s causing the problem. The dev certificate generated by visual studio is for some reason not compatible with http2. I saw this discussion on Github so it must not be just me :).

That being said, I do want to say that I’m following your tutorial and enjoying it very much. You are building it step by step breaking it down so we can absorb it one step at at time. Fantastic job! Thank you!!

Thanks Daniel for sharing. I’ve faced http2 issue only in win7, once win10 was installed http2 support was out of the box. I am not sure thiugh, why do you have such a problem.

For anyone else who has this issue, it is caused because of an incompatibility of .net core dev-cert with HTTP2, so to disable HTTP2 for this project just add this to your appsettings: and you should be good at least in chrome

“Kestrel”: {
“EndpointDefaults”: {
“Protocols”: “Http1”
}
}

I have the same issue, if i used 5005 with https i get:
The webpage at https://localhost:5005/ might be temporarily down or it may have moved permanently to a new web address.
ERR_HTTP2_INADEQUATE_TRANSPORT_SECURITY

If I use 5006 it loads the page but I cannot login