Re: Need to know when user log's in again.

Why not do it in the Login page before you redirect after a successful
login?

Neither Session start nor that global.asax event are appropriate for this
kind of action.

--
----
700cb Development, Inc.
http://www.700cb.net
..NET utilities, developer tools,
and enterprise solutions

"Edwin Knoppert" <news@xxxxxxxxxxxxxx> wrote in
news:43956c4b$0$2332$ba620dc5@xxxxxxxxxxxxxxxxxxx:

> I have a forms based authentication.
> On each Application_AuthenticateRequest() i set the ticket again.
> I want to store the last login date/time
> On Session_Start() the user isn't authenticated yet.
> On Application_AuthorizeRequest() i can not set a session var to
> prevent multiple writes.
> The App.. events are called on each request.
>
> What is the best approach?
> I'm looking for a one-time executed event when the user get's
> authenticated. I do not really care for session start, even that one
> is called multiple times.
> (Prob. due a redirect() i have here)
>
>
> Thanks!
>
>
>

.

Relevant Pages

  • Re: Force Relogin. IIS6, ASP.NET app, IE6+ browser
    ... now it appears you are suggesting I either write a custom authentication ... cookies/tokens involved; IIS has no idea what a session is; IIS does ... not prompt with a login dialog. ... The problem you face is that a browser will automatically attempt ...
    (microsoft.public.inetserver.iis.security)
  • Re: Default.aspx - newbie Q`
    ... check and redirect to the ReturnURL or Selected.aspx depending on the case. ... > and replace it with something that takes then straight to the login page. ... >> Curt Christianson ... >>> authentication ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Default.aspx - newbie Q`
    ... check and redirect to the ReturnURL or Selected.aspx depending on the case. ... > and replace it with something that takes then straight to the login page. ... >> Curt Christianson ... >>> authentication ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ASP 2.0 Membership API
    ... After successful authentication, you want to redirect back to the original application, but the returnURL parameter contains only /App1 as the URL. ... The solution to that problem is adding a local login page to the application that does a manual redirect to the central authentication application. ... if not you have to use cookieless auth ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Detecting Failed Authorization
    ... after every authentication request and before the user ... is redirected to any login page. ... > "Ken Dopierala Jr." ... >> 'Redirect where you want the user to go. ...
    (microsoft.public.dotnet.framework.aspnet)
Loading