Catching authentication session timeout during remote callback

[Sosh]

Hi,

I wonder if anyone knows how an application that employs remote
scripting/callbacks should deal with an authentication timeout during a
callback? At the moment my application just stops working until I refresh
the page and log in again. I'm not really sure what its going in - perhaps
the framework is trying to redirect the callback result to the login page?

Any ideas?

Thanks,

S

 

[Marina]

what is the remote scripting callback mechanism? Are you just making the
HTTP calls yourself using javascript, or using something else?

If you are just doing this yourself, you probably need to have your calls
return a special code of some sort saying the session timed out. Then you
need to figure out the best way for your user to re-authenticate. Maybe you
need to pop open a login dialog for the user so that the user can log in
again, and then re-try to original remote call.

 

[Sosh]

Hi Marina,

I'm using the callback framework provided with asp.net2, ie.
RaiseCallbackEvent() with my stuff bolted on top of it. At the moment the
server does not seem to be replying to the callback at all when one is
requested after the timeout. At the moment the only way I can think of
dealing with this is having the browser refresh the page after a certain
time has elapsed without a callback response - but this is very messy.

Thanks.

 

[Bruce Barker]

ajax callback pages should not use forms authenication. you should pass a
private secuirty token as a parameter to the callback that your ajax page
checks. MS has not worked on this very much, so you are pretty much on your
own.

-- bruce (sqlwork.com)

 

[Sosh]

You're kidding!

What a pile of ****!

Thanks for the info though.