windows-authentication

问题 I'm actually working on an website where users login via windows authentication. My problem is, that actually all users have to login whenever they open our webpage. I wonder if it is possible to keep that windows authentification alive? Maybe with cookies? I implemented the authentification by adding this to my Startup.cs : services.Configure<IISOptions>(options => { options.AutomaticAuthentication = true; }); services.AddAuthentication(IISDefaults.AuthenticationScheme); And activating

问题 I have a project, It's a web application that requires Windows Authentication. I've setup an Active Directory at home using my NAS virtualization. Then I've created a VMWare Server for IIS which is a member of that domain on my desktop which I also use for development. I've created the Web API and installed it into that VMWare server. When I call a routine directly, it works and return results but when I use the Web API routine from my javascript web application I keep on getting 401 error. I

问题 I recently had a nasty issue getting Windows Authentication to work on a local instance of IIS 7.5 (Windows 7 Pro) to an ASP.net 4.0 site. I followed the basic steps. IIS Authentication Disable Anonymous Authentication Enable Windows Authentication Edit web.config <authentication mode="Windows" /> This did a nice job of enabling Windows Authentication but every attempt to login was rejected and ultimately returned a 401.1 error. This is where the problem started. There appear to be many

问题 Chrome 86 (and prior), Edge, Curl, and IE all are able to do cross-origin Windows Authentication against my IIS 10 ASP.NET service on Windows 2019 machine without any problem. But Chrome 87 fails with "Access to XMLHttpRequest at 'https://[REDACTED]' from origin 'http://[DIFFERENT]' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested" Weirdly - Chrome 87 works with the identical ASP.NET service running in IIS 7.5 on a Windows 2008 machine (don

问题 Chrome 86 (and prior), Edge, Curl, and IE all are able to do cross-origin Windows Authentication against my IIS 10 ASP.NET service on Windows 2019 machine without any problem. But Chrome 87 fails with "Access to XMLHttpRequest at 'https://[REDACTED]' from origin 'http://[DIFFERENT]' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested" Weirdly - Chrome 87 works with the identical ASP.NET service running in IIS 7.5 on a Windows 2008 machine (don

问题 I've created a Web Api 2 app which will only be used on the corporate network. I've read about Windows authentication in Web API so it seems to be possible. But I need to figure out the proper implementation for this. I've included the following xml in my Web.config: <system.web> <authentication mode="Windows" /> </system.web> I seem to remember some type of event hook in old school webforms app. Something like BeginRequest() where a security check could be made before rendering a page. I

来源： https://stackoverflow.com/questions/30091833/accessing-sharepoint-in-r-with-windows-authentication

来源： https://stackoverflow.com/questions/30091833/accessing-sharepoint-in-r-with-windows-authentication

来源： https://stackoverflow.com/questions/52146938/how-to-combine-the-windows-authentication-and-jwt-with-net-core-2-1

来源： https://stackoverflow.com/questions/52146938/how-to-combine-the-windows-authentication-and-jwt-with-net-core-2-1