-
Notifications
You must be signed in to change notification settings - Fork 25.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WinAuth topic updates #12554
WinAuth topic updates #12554
Conversation
Updates
5edab71
to
8b00898
Compare
@scottaddie Ur 1st author on this ... do you want to look? |
aspnetcore/security/authentication/windowsauth/sample_snapshot/Program_GenericHost.cs
Outdated
Show resolved
Hide resolved
aspnetcore/security/authentication/windowsauth/sample_snapshot/Program_WebHost.cs
Outdated
Show resolved
Hide resolved
Co-Authored-By: Scott Addie <10702007+scottaddie@users.noreply.github.com>
We discussed on another PR not cluttering the topics with them. Namespaces are easy to find. However, the solution on the last commit removes the guesswork. I link right to it and call it out in text. |
@guardrex If that's what was discussed in another PR, then roll with it. I've been out of the loop. |
@scottaddie Note WRT the merge ... The PU hasn't looked at these updates. We could just ask them to look at the live topic and see if there are any probs. As you saw, the vast majority of the changes here are just in topic layout. Alternatively, the merge could be reversed and we let them come on at the doc-a-thon and 👀. |
@guardrex We'll let them look at the doc-a-thon. |
Sure ... sounds good. ... and don't forget our readers in the meantime. lol They know full well what to do when they see a 🐲 Rex Franken Doc™️ 🐲 ... it's a lot of pitchforks and torches coming my way if these topic revisions go wrong. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, but clarifying the IIS scenarios would help.
|
||
The **Web Application** template available via Visual Studio or the .NET Core CLI can be configured to support Windows Authentication. | ||
Configuration for launch settings only affects the *Properties/launchSettings.json* file and doesn't configure the IIS or HTTP.sys server for Windows Authentication. Configuration of the server is explained in the [Enable authentication services for IIS or HTTP.sys](#authentication-services-for-iis-or-httpsys) section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So what does it affect? (IIS Express)
|
||
Depending on the hosting scenario, follow the guidance in **either** the [IIS](#iis) section **or** [HTTP.sys](#httpsys) section. | ||
|
||
### IIS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And Express?
In-proc and out-of-proc?
@Tratcher I'll open a new issue with those remarks and work it asap. Although I had the "PU" label on this, I should have said something in the comments. |
Fixes #12102
Fixes #12144
Internal Review Topic
Revised outline