>The way I've done this in the past was to store the credentials on the flex >client and re-authenticate the user with these using the CFLOGIN framework. > This way the responsibility for continuing the session is on the flex side >of things.
I'd really rather not do this as it would mean using a login specific to the application. My current method uses their local machine login (which changes every 90 days)which is far more user-friendly as they don't have to remember a second login that's only for this tool. But it does require having to handle the authentication in CF. And right now, it's working great, no timeout issues and very little need for the users to do anything.... if it wasn't for the issue with the error handling --- Mary Jo ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:343063 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
