Last post Jun 06, 2017 04:55 PM by ryanbesko
Jun 06, 2017 04:51 PM|DoctorWho|LINK
I've been working on an ASP.NET MVC project off-and-on, as I have the time to do so. Things at work are slowing down so I've gone back to the MVC project. I've gotten it ready to put out there, but now realize that I've made a mistake when creating the project.
Back when I created it I did so with no membership or authorization in mind.
(Quick aside, this project is meant to be used by a couple of us in IT who need to do occasional maintenance on some data. I used Visual Studio 2015 to create it.)
Now I'd like to get it out there so that those of us in the IT group can use it for those regular maintenance tasks we need to do. So I'm going to get a URL to place this app on one of our servers and will get the system admins to create an Active Directory
Group, and put those of us who do the maintenance into that AD Group. In reading the docs such as
Introduction to ASP.NET Identity, I've realized my mistake/oversight of not having added organizational accounts to start with. My bad.
So I want to know is it possible for me to add organization accounts to this MVC project now, after all the work I've already put into it? Or do I have to start over, create a whole new project and copy over the views, models and controllers from the old
Jun 06, 2017 04:55 PM|ryanbesko|LINK
Just put this in the Web.config file in the root of your project. NOT the one in the Views folder.
<authentication mode="Windows" />
<deny users="?" />
The rest is IIS configuration. Turn off Anonymous Auth. and turn on Windows Auth.