DISQUS

BillBuchan · 2 months ago

And last but not least. If you dont like your flex app timing out after 30 minutes of inactivity, its very simple to have a flex timer - activated on startup - fire off an event every 5 or 15 or whatever minutes, which will then use a similar http call to the domino server for information. This will in turn update the cookie, and the user will remain logged in.

We, for instance, use a call to a web service to refresh a 'view' on the flex app from a View from Domino.

---* Bill

markbarton · 2 months ago

Of course if you revert your server to Basic authentication you don't have to do anything as the browser will present a challenge when the Flex app first attempts to access the Domino Application and everything works as expected. Accept of course Basic authentication isn't very secure ;-)

I followed the same approach but instead redirected to a page marked as XML to gather some current user information (Commonname, roles etc).

rostag · 1 week ago

Steve,
your method works for me with one exception: I use "login" command, not "logon" in the ".../names.nsf?logon" url. Maybe I missed something - I am so Domino newbie... anyway, your recipe helped me to perform my task. Thank you for the great example.

And - Happy New Year!