I'm trying to create an application that mixes windows authentication with forms authentication. The idea is simple: whenever the browser is able to use NTLM and the user has permissions, then he should be automatically logged in. When that doesn't happen, the user must be redirected to a page that shows a login form. I've found an old article (http://mvolo.com/iis-70-twolevel-authentication-with-forms-authentication-and-windows-authentication/) and I've also found a sample online (https://github.com/patuww/P2000DemonstrationProjects/tree/master/MultiAuthExample) which should be able to solve my problem.
Unfortunately, it's not working and I was wondering if there's any more info about this.
Thanks.
Luis
Related
We are a software dev company company with a product that is deployed at our client's site. Recently, we started seeing an issue with our login in conjunction with Siteminder.
They have Siteminder turned on but we are not integrating with it for SSO. They get to our login page just fine. When a user inputs their login credentials our application returns a login error and does not allow them to login.
Upon further investigation, we found that our login process is receiving 2 different requests! One with the correct username and PW and another request is blank username and PW. As soon as we turn Siteminder off, it works correctly.
We are not sure if this is an issue in our code or with Siteminder's setup. We have other instances of the application that work correctly. We did no code changes to integrate with SM when we first deployed and it was working fine before. We sent a code update and then it started not working. It all points to us but we cannot find it in the code. Any help here would be great! We are not sure how SM really works with this.
This probably is not something that Siteminder is causing. Did you trace the JS requests to see if there are two submits being done on the page
Generally WE Disable the webagent to remove the siteminder component from the infrastructure. if the end user is able to access application without the siteminder component the the problem relise on siteminder part.
and if user is facing an issue while accessing the an application without the siteminder composts . then there is no issues on siteminder components.
I am working on a project of developing a web UI. The project requires .NET implementation. I currently published the website on Windows server 2008 with IIS 7.5 for testing. The project asks for and login/out page as the entrance to the main UI. The login/out page should asks for username and password with some security questions. And it also enables user to change and save the password. The authentication technique has to be implemented using digested authentication.
I have already tested the digest authentication after enabling it in IIS. It works good with popping up a window asking for the username and password.However, I have a doubt whether the digest authentication allows for customized login/out page and ability of changing and saving the password (which will most likely be realized with form authentication to the best of my knowledge). I believe there might be (or not?) some ways of doing it, anyone can guide me to some references or sample codes?
Try this article: http://www.eggheadcafe.com/articles/20030701.asp
And maybe this one: http://msdn.microsoft.com/en-us/library/Ee817643%28pandp.10%29.aspx
Hi does someone have a link or can offer some guidance on HOW the facebook C# SDK could be used to provide access credentials to facebook along side ASP.Net membership?
Basically what i would like to do is have some kind of connect button on my profile view that when clicked opens the facebook app authorization window, if the user signs in and agrees the facebook auth cookie is returned or accessible so i can store in locally in my DB.
I originally tried to figure out how to do this using dotnetopenauth about 9 months ago and eventually gave up. ANY help is appreciated. thanks!
I haven't done it, but it shouldn't be too hard I think.
I'm assuming you already know how to "authenticate" users with Facebook using the C# SDK. At that very point where you consider them "authenticated" hook into it and perhaps use FormsAuthentication.SetAuthCookie() to manually authenticate the user from the default ASP.NET membership's perspective.
I have to create a simple ASP login page. We're not using Windows authentication or anything like that. The project is a conversion from a legacy VB6 program. Login accounts and passwords are stored in a SQL table, not the way to do it, but it is what it is. I can call the old login functions and redirect the window based on the return values.
Is there a decent-looking login form out there I could use? I tried the login control in the toolbox, but that thing seems to be married to Windows authentication.
I really just need an empty control that looks good. Any ideas?
Thanks,
Jason
Google for "Login Templates".. artfans.info/login-page-template-tag-style – Nikhil Bhandari
I am trying to figure out how to implement an ASP.NET page with Windows Authentication without getting that annoying IIS login box.
I currently have 3 domains in my network so all the people logging in would have to prefix their user names with the domain. This is not user friendly. I would like to have a custom login page that would have a domain combo box.
Most examples I found implement this using Form security, however I need Windows Authentication since I want to connect to the SQL server using Integrated Authentication rather than a hard coded user name and password.
Does anyone know of a good article or sample code that shows how to implement this?
The following links to an article that explains how to authenticate a windows user using forms authentication, it uses a call to the native win32 api function LogonUser to acheive this. This way you can design your own custom login page with a drop down list to select a domain. Take a look, perhaps it will help.
Windows Authentication using Form Authentication
To get this setup so you don't have the authentication prompt, you are going to need to have the domains trust the accounts from one another. This article should get you pointed in the right direction:
http://technet.microsoft.com/en-us/library/cc787646%28WS.10%29.aspx