I have been using the DNNSpired DS_PortalTrafficDirector module up until now and it has been working OK.

 

However I now have a different issue:

 

I have different departments accessing the same portal and when they logout they need to be redirected to different external, NON-DNN URL’s. Now I have written a module to do this successfully.

 

However my problem is when the user is timed out – the DS_PortalTrafficDirector can redirect depending on user roles, but when a user is timed-out, the module doesn’t work – I presume because the user role information is not available.

 

Can anyone offer any suggestions as to how I can redirect different users to different sites upon time out?

 

Any help would be REALLY appreciated.

 

Your client page does not know when the server decides that the session has timed-out....you have to wait for the user to make a new server request before you can act on a timeout.
 
When the client does make a server request after a timeout, you can forward to a custom login page if your server code includes the following:
  
  if(Session["Session_name"]==null)
  Response.Redirect(”Login.aspx”); 

 
A client-side approach would be to set a meta tag in each page to auto-forward to your special login page after the default timeout period (usually 20 minutes for IIS).  Such an approach can be accomplished in environments where you do not have access to change server code.  This simple client-side approach will not, however, take into account sessions that are extended by background asynch AJAX calls which means that, depending on your UI, you could have an active user interacting via an AJAX-enabled UI who remains on a single page and is wrongly forwarded to the login page after 20 minutes due to not having initiated a full-page refresh before the 20-minute timer is up. 
 
You can get fancy with AJAX, javascript timers and browser input event handlers to keep track of extending the session yourself while clients are active but not making server requests (when someone is filling in a very long form, for instance) and auto-forwarding to a login page after a certain period of time + session timeout.  I've done this very thing before and, though not overly hard, it's also not trivial.  I wouldn't recommend it except in cases where you want to auto-extend sessions for active users and/or you wish to warn a user of an impending timeout before the timeout actually occurs.
 
Hope that helps!
-mamlin