Centralized single sign-on method and system for a client-server environment

• US 20020184507A1
• Filed: 05/31/2001
• Published: 12/05/2002
• Est. Priority Date: 05/31/2001
• Status: Abandoned Application

• Current Assignee: ProAct Technologies Corp. (HRSoft, Inc.)
• Original Assignee: ProAct Technologies Corp. (HRSoft, Inc.)
• Inventors: Makower, David, Sachs, Jay, Schwell, Steven
• Application Number:
  US09/871,525
• Publication Number:
  US 20020184507A1
• Time in Patent Office: Days
• US Class Current: 713/182
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32

Abstract

The present invention generally relates to the field of secure centralized single sign-on and session maintenance for web servers on the Internet. In a preferred implementation, a single sign-on protocol for use by web servers is independent of the actual authentication mechanism used by any of the individual web servers accessed by the user. Users authenticate themselves with any one of a group of federated servers so that a user does not need to be re-authenticated by other servers in the federation. In a preferred implementation there is also a centralized server that provides for the transparent sign-on, session management, and session termination within each server in the federation of servers, and each federated server communicates with the central sign-on server.

Claims

1. A method for transparent sign-on in a client-server environment, the method comprising the steps of:

receiving an encrypted communication on an originating server from a client, the client using a browser;

creating a challenge at the originating server;

sending an encrypted communication to a central sign-on server from the originating server;

receiving an encrypted communication on the originating server from the central sign-on server, wherein the communication received on the originating server includes a response to the communication sent to the central sign-on server;

updating a client session on the originating server; and

sending another encrypted communication to the central sign-on server from the originating server.

2. The method of claim 1, wherein the step of creating a challenge further comprises the step of recording on the originating server a URL requested by the client browser, a time at which the challenge was generated, and a federation identification.

3. The method of claim 2, wherein the step of sending an encrypted communication to a central sign-on server further comprises the steps of redirecting the client browser to the central sign-on server and sending to the central sign-on server the federation identification, the challenge, and a server identification.

4. The method of claim 1, wherein the step of receiving an encrypted communication on the originating server from the central sign-on server further comprises the step of receiving a digital signature of the central sign-on server for all information communicated from the central sign-on server.

5. The method of claim 4, wherein the step of receiving an encrypted communication on the originating server from the central sign-on server further comprises the step of receiving a redirection of the client browser on the originating server.

6. The method of claim 5, wherein the step of receiving a redirection of the client browser further comprises the steps of receiving a parameter indicating that no session was present on the central sign-on server, the challenge, and the digital signature on all of the information communicated from the central sign-on server.

7. The method of claim 5, wherein the step of receiving a redirection of the client browser further comprises the steps of receiving a parameter indicating that a session was present on the central sign-on server, the challenge, and the digital signature on all of the information communicated from the central sign-on server.

8. The method of claim 1, wherein the step of creating a client session on the originating server further comprises receiving authenticating information from the client browser.

9. The method of claim 8, wherein the step of updating a client session on the originating server further comprises creating a client session on the originating server.

10. The method of claim 1, wherein the step of sending another encrypted communication to the central sign-on server from the originating server further comprises the step of creating a digital signature on all information sent to the central sign-on server.

11. The method of claim 10, wherein the step of sending another encrypted communication to the central sign-on server further comprises the step of sending the challenge, a session time-out value, a parameter specifying that a session has been created on the originating server, a log-in identification of the client for which the session has been created, and the digital signature.

13. The method of claim 12, wherein the step of receiving an encrypted communication on the central sign-on server from the web server comprises the steps of receiving a redirection of the client browser on the central sign-on server and receiving a federation identification, a challenge, an identification of the web server, and a digital signature of the web server.

14. The method of claim 12, wherein the step of recognizing the client on the central sign-on server further comprises the steps of creating a cookie on the client browser and creating a record of the client on the central sign-on server.

15. The method of claim 14, wherein the step of creating a record of the client on the central sign-on server further comprises the step of using the cookie and the identification of the originating server as a concatenated primary key.

16. The method of claim 12, wherein the step of recognizing the client on the central sign-on server comprises the steps of accessing a cookie on the client browser and looking up the client on the central sign-in server based on the cookie.

17. The method of claim 16, wherein the step of looking up the client based on the cookie comprises looking up the challenge associated with the client session from a record on the central sign-on server.

18. The method of claim 12, wherein the step of sending an encrypted communication to the web server from the central sign-on server comprises the step of creating a digital signature for all information communicated to the web server.

19. The method of claim 18, wherein the step of sending an encrypted communication to the web server from the central sign-on server further comprises the steps of redirecting the client browser back to the web server and communicating the client log-in identification for the current client session, the challenge, and the digital signature.

20. The method of claim 18, wherein the step of sending an encrypted communication to the web server from the central sign-on server further comprises the steps of redirecting the client browser back to the web server and communicating a parameter indicating that no session was present on the central sign-on server, the challenge, and the digital signature.

21. The method of claim 12, wherein the step of receiving another encrypted communication on the central sign-on server further comprises the steps of receiving an identification of the web server, a challenge, a session time-out value, and a digital signature for all information sent to the central sign-on server.

22. The method of claim 21, wherein the step of receiving another encrypted communication on the central sign-on server further comprises receiving a parameter specifying that a session has been created on the web server and a log-in identification of the client for which the session has been created.

23. The method of claim 12, further comprising the step of updating a record of the client session on the central sign-on server.

24. The method of claim 23, wherein the step of updating a record of the client session on the central sign-on server comprises the step of verifying a digital signature of the web server.

25. The method of claim 24, wherein the step of updating a record of the client session on a central sign-on server further comprises the steps of creating a record on the central sign-on server of the client session and the session time-out value.

27. The method of claim 26, wherein the step of running a session freshening task comprises the steps of looking up a list of active sessions on the web server and determining whether a session will expire on the central sign-on server before the next time the session freshening task runs.

28. The method of claim 27, wherein the step of sending an encrypted communication to the central sign-on server from the web server comprises the step of sending a server identification of the web server, the challenge used in creating the session, a new time-out value for the session, and a digital signature for all information sent in the message.

29. The method of claim 28, wherein the step of recognizing a session on the central sign-on server comprises the steps of verifying the digital signature and using the challenge to look up a record of the sessions on the central sign-on server.

30. The method of claim 26, further comprising the step of updating a client session record associated with the session on the central sign-on server.

31. The method of claim 30, wherein the step of updating a client session record comprises the step of updating a time-out value for the session on the central sign-on server.

12. A method for transparent sign-on in a client-server environment, the method comprising the steps of:

receiving an encrypted communication on a central sign-on server, wherein the communication is from a web server;

recognizing a client on the central sign-on server;

sending an encrypted communication to the web server from the central sign-on server; and

receiving another encrypted communication on the central sign-on server from the web server.

26. A method for session maintenance in a transparent sign-on client-server environment, the method comprising the steps of:

running a session freshening task for sessions on a web server;

sending an encrypted communication to a central sign-on server from the web server; and

recognizing a session on the central sign-on server.

32. A method for session maintenance in a transparent sign-on client server environment, the method comprising the steps of:

recognizing a client on a web server;

terminating a client session on the web server;

sending an encrypted message to a central sign-on server;

recognizing the client on the central sign-on server;

updating a record of a session associated with the client;

sending an encrypted communication to a second web server, the second web server having a current local session associated with the client; and

terminating a local session associated with the client at the second web server.

33. The method of claim 32, wherein the step of recognizing the client on the web server comprises the step of looking up a challenge associated with a client session.

34. The method of claim 33, wherein the step of recognizing the client on the web server comprises receiving a communication from the client.

35. The method of claim 33, wherein a digital signature is created for all information communicated to the central sign-on server.

36. The method of claim 35, wherein the step of recognizing the client on the central sign-on server comprises the steps of verifying the digital signature of the web server and using the challenge to look up a record of any current session associated with the client.

37. The method of claim 32, wherein the step of updating a record of a session associated with the client comprises deleting a record on the central sign-on server.

38. The method for claim 32, wherein the step of sending an encrypted message to a second web server further comprises sending the encrypted message to each web server for which the central sign-on server has a record of an active session associated with the client.

39. The method of claim 38, wherein the step of sending an encrypted message to a second web server further comprises the step of sending a parameter indicating that the client session is terminated and a digital signature of the central sign-on server.

40. The method of claim 39, wherein the step of terminating a local session associated with the client at the second web further comprises the step of verifying the digital signature of the central sign-on server.

41. A system for secure single sign-on in a client-server environment, the system comprising:

a server, the server configured to communicate with a client;

a central sign-on server, the central sign-on server configured to communicate with the client and the server; and

means for identifying the client on the central sign-on server.

42. The system of claim 41, wherein the means for identifying the client on the central sign-on server comprises a Single Sign-On Support URL located on the server.

43. The system of claim 42, wherein the Single Sign-On Support URL comprises means for creating a challenge when the client initiates communication with the server, means for redirecting the client browser to the central sign-on server, means for communicating the challenge to the central sign-on server, and means for receiving a communication from the central sign-on server.

44. The system of claim 41, wherein the server and the central sign-on server are co-located on the same server.

45. The system of claim 41, wherein the server is a member of a federation of servers, where each member of the federation of servers is configured with a server identification, and configured to use a similar policy with regard to session management as a second server in the federation of servers.

46. The system of claim 45, wherein the server in the federation of servers is configured to send encrypted messages to the central sign-on server and receive encrypted messages from the central sign-on server.

47. The system of claim 46, wherein the central sign-on server is a central sign-on server for more than one federation of servers, each federation of servers being configured with a unique federation identification.

48. The system of claim 47, wherein the central sign-on server is configured to create a digital signature that is recognized by the server in the federation of servers.