Re: AuthenticateRequest in Global.asax and a custom HTTP Module

From: Leslie (Leslie_at_discussions.microsoft.com)
Date: 05/25/05 

Date: Wed, 25 May 2005 11:04:38 -0700

Thanks for helpine me here. If I understand you correctly, I think you are
talking about form authentication. However, since I am writing a web service
application, I can't use this approach. That is why I am thinking to use
AuthenticateRequest from either the Blobal.asax or a custom HTTP module. But
I am not sure about the difference of these two. Do you know?

"Brock Allen" wrote:

> > 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
>
>
>
>
>

Relevant Pages

  • Re: AuthenticateRequest in Global.asax and a custom HTTP Module
    ... Dominick Baier - DevelopMentor ... > you are talking about form authentication. ... > Blobal.asax or a custom HTTP module. ... >> Authentication is done in your custom login page. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: AuthenticateRequest in Global.asax and a custom HTTP Module
    ... > I think that I could put my authentication code in AuthenticateRequest ... > event in either Global.asax or in a custom HTTP module. ... Authentication is done in your custom login page. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • RE: Form Security and WebService
    ... it has to do with the fact that you have a membership store in SQL ... that uses windows authentication). ... call the SharePoint web service to provision the user. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Problem When Calling Web Method Of Web Service From Pocket PC 2003.
    ... > NTLM Authentication is not supported in the CF. ... > Now that I have changed the Web site and Web Service to use Digest ... >> Alex Feinman ... a Desktop application and a Pocket PC 2003 application. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: Active Directory authorization
    ... AD should be fine as a source for authentication for your web service. ... The easiest way to use AD for authentication is to just use the transport layer authentication schemes built in to IIS. ... For app level authorization, I'd suggest checking out Microsoft's Authorization Manager framework. ... every applications. ...
    (microsoft.public.windows.server.active_directory)