Re: Additional steps after authentication

I thought about this. But it seems like a hack, plus we are not using
session state.

My other thought was to use UserData in FormsAuthenticationTicket to store
some flag indicating that checks were successful. The I would check in
Application_Authenticate request for this flag. Any comments on this
approach? One thing that bothers me is that at some point I would have to
override authentication ticket to change UserData. Can this screw up forms
authentication infrastructure?

Alex


On Thu, 22 Feb 2007 18:50:39 +0100, Efran Cobisi <[email protected]>
wrote:

>Hi Alex,
>
>I've had the very same problem in a web app some time ago. My solution
>was to stay with FormsAuthentication but do not authenticate the user
>until she completed the required checks; in that case, I stored a state
>value in the user session, which basically would indicate that the user
>has been already checked against username/password match but it has to
>complete the aforementioned checks. Once the checks completed, I'd
>authenticate the user within FormsAuthentication.
>
>HTH,
>
>Efran Cobisi
>http://www.cobisi.com
>
>Alex Ivanoff wrote:
>> I have an application using forms authentication with the following
>> requirement. After user logs in the application needs to to perform some
>> checks. If all checks are satisfied user is redirected to the original
>> page she requested. If one or more checks fail user is redirected to
other
>> page to make some changes. After that checks are performed again until
all
>> of the ckecks are satisfied and user is redirected to the original page.
>> What is the best way to accompish something like this?
>>
>> Thank you,
>> Alex

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com