Issue authenticating with Windows Auth #30075
Unanswered
adamdriscoll
asked this question in
Q&A
Replies: 1 comment
-
A) You can use kestrel's connection logging to capture the headers. The auth headers can be decoded using standard tools to check that the expected SPNs are being included. https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel/endpoints?view=aspnetcore-5.0#connection-logging |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have a customer that is running our product built on ASP.NET Core in their environment and cannot authenticate with Windows Auth. They have setup an SPN for the host name and service account following this documentation.
The service itself is doing very little when it comes to configuration.
The SPN is configured with the FQDN for the host name. They are unable to access the website by host name or FQDN and the following error is shown in the log. They can access the site by IP Address and it authenticates correctly.
I'm mostly just looking for debugging steps to provide them. I know our service works in other environments but am at a bit of a loss at what to tell them to look into. It looks like the SPN and service account are configured correctly. The service account was set to deny logon interactively so not sure if that's a problem.
I've found a few outstanding issues but they don't seem to apply here:
Beta Was this translation helpful? Give feedback.
All reactions