Re: AuthenticateRequest in Global.asax and a custom HTTP Module
From: Brock Allen (ballen_at_NOSPAMdevelop.com)
Date: 05/25/05
- Next message: Leslie: "Re: AuthenticateRequest in Global.asax and a custom HTTP Module"
- Previous message: Brock Allen: "Re: Folder Authorization."
- In reply to: Leslie: "AuthenticateRequest in Global.asax and a custom HTTP Module"
- Next in thread: Leslie: "Re: AuthenticateRequest in Global.asax and a custom HTTP Module"
- Reply: Leslie: "Re: AuthenticateRequest in Global.asax and a custom HTTP Module"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 25 May 2005 10:51:30 -0700
> I think that I could put my authentication code in AuthenticateRequest
> event in either Global.asax or in a custom HTTP module. However, I
> don't know what is the difference between them. And is there any
> implication if I make the choice of one way or the other?
Authentication is done in your custom login page. Once you are confident
the user has provided proper credentials you then want to call FormsAuthentication.SetAuthCookie
or FormsAuthentication.RedirectFromLoginPage. This will issue a cookie that
will identify the user.
So, in short, you just need to build the login page.
-Brock
DevelopMentor
http://staff.develop.com/ballen
- Next message: Leslie: "Re: AuthenticateRequest in Global.asax and a custom HTTP Module"
- Previous message: Brock Allen: "Re: Folder Authorization."
- In reply to: Leslie: "AuthenticateRequest in Global.asax and a custom HTTP Module"
- Next in thread: Leslie: "Re: AuthenticateRequest in Global.asax and a custom HTTP Module"
- Reply: Leslie: "Re: AuthenticateRequest in Global.asax and a custom HTTP Module"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|