Single Sign-On and Session Timeout - How to do it?

Hi Forum

� 

I need to improve the performance and scalability� of some web applications that use a custom single sign-on solution. The web apps are located on different servers and have different domains. The problem today is that each request to any of the applications make a call to a central single sign on server. The signle sign-on server holds global users and keep the sessions. A timestamp is updated on each authentication request� of� the sessionId.

� 

It works like this for all the web applications:

� 

1. User accesses page. ( /page.aspx=SessionId=xx )

� 

2. Web server calls single sign-on server to verify whether the session is valid by passing the sessionId and IP address of the client to the single sign-on server.

� 

3.� Web applications can link directly to� other web applications, even pages d ...