Of Men with the Brain on Both Sides and a Utopian Cult56 days beforeHas it really been that long since my last post?Complete Credentials Screening

Better Credentials Screening2004In my first post about credentials screening, I’ve offered sample code, which…Here’s the latest iteration of the Credentials Screening module (for more information see this and this posts). It further improves the way credentials screening operates, introducing things like Windows authentication cookie reminder (because sometimes Explorer “forgets” that it had already authenticated with the site and issues a new challenge), better browser detection (since no other browser supports silent authentication, only MSIE will invoke the credentials screening process), corrected support of Forms authentication, and last, but not least — Authenticate event, which your application can subscribe to by simply implementing a CredentialsScreening_Authenticate method in the Global.asax.cs class. The signature of your method should look like this:

Credentials Screening: Windows Authentication without a Login Dialog Box2004The screening function must be contained in that first pageprotected void CredentialsScreening_Authenticate(Object sender, EventArgs e) { /* body of your method */ }

This method will be called any time the Credentials Screening module successfully authenticated a user. Neat, huh? Oh, by the way, almost forgot:

If you want to explicitly make the login dialog pop-up (for example, you have a “Login” button for those who couldn’t authenticate through screening), use this static method to retrieve it:

public static string ScreeningModule.GetManualLoginUrl(HttpRequest request);

Progressive Enhancement: Couldn’t have said it better myselfeight days afterJeremy Keith has a very nice and complete summary of pitfalls of…Well, this about sums it up. Let me know if you find any more bugs or opportunities for improvement.