Sharing a sign-in among software applications having secured features

• US 20040111644A1
• Filed: 12/04/2002
• Published: 06/10/2004
• Est. Priority Date: 12/04/2002
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Gupta, Vishal, Coloma, Ignacio Ariel, Saunders, Stillman T.
• Granted Patent: US 7,254,831 B2
• Time in Patent Office: Days
• US Class Current: 713/202
• CPC Class Codes: G06F 21/41 where a single sign-on provides access to a plurality of computers

Abstract

In the present invention, when one open or running software application having secured features enters an access signed-in or logged-in state, other open or running software applications having secured features enter a ready signed-in state automatically, without prompting user intervention. The same operation that signed-in or logged-in the initial software application will transition other software applications that are presently open, active to run, or that start in run mode to a ready signed-in state. The access signed-in state fully authenticates the user'"'"'s identity and grants access to secured features. The ready signed-in state places the software application in a state of readiness to authenticate and access secured features without prompting user intervention. One feature of the present invention is the sharing of a sign-in or login credential (e.g. username and password) and the processing of the shared credential in order to provide a universal, shared sign-in session between open software applications having secured features. This feature helps provide a user experience that in effect, has only one sign-in or login session for software applications with secured features.

Claims

1. A method for sharing a sign-in operation among two or more software applications, wherein the software applications each have one or more secured features comprising:

receiving a request to sign-in to a first running software application;

processing a credential to enter an access signed-in state within the first running software application to grant access to one or more secured features;

in response to the access signed-in state, detecting whether one or more other software applications are running; and

in response to the access signed-in state and to one or more other software applications running, transitioning one or more other running software applications to a ready signed-in state with access to the credential.

2. The method of claim 1, wherein the other running software applications comprise software applications in run mode and software applications that are starting.

3. The method of claim 2, wherein processing a credential comprises:

receiving a credential;

detecting whether the credential is authentic; and

in response to the credential being authentic, receiving and storing authentication information, writing the credential to a shared memory, and sending notification indicating an access sign-in has occurred to the other running software applications.

4. The method of claim 3, wherein transitioning the other running software applications comprises:

receiving notification that the access sign-in has occurred; and

in response to receiving notification, changing an interface of each software application in run mode to indicate a signed-in state.

5. The method of claim 4, wherein transitioning the other running software applications further comprises:

detecting whether a credential is stored in the shared memory; and

in response to the credential being stored, changing an interface of each software application starting to the signed-in state.

6. The method of claim 5, wherein the signed-in state comprises the access signed-in state or the ready signed-in state.

7. The method of claim 6, further comprising:

receiving a request to access a secured feature within a software application when the software application is in the ready signed-in state;

in response to receiving the request, retrieving the credential from the shared memory;

detecting whether the credential is authentic; and

in response to the credential being authentic, receiving and storing authentication information for accessing the secured feature of the software application whereby the software application is transitioned from the ready signed-in state to the access signed-in state and the secured feature is accessed.

8. The method of claim 7, wherein detecting whether the credential is authentic comprises:

transmitting the credential for authentication;

verifying an identity of the credential; and

in response to the identity of the credential being verified, validating the credential.

9. The method of claim 8, wherein the credential is stored and transmitted in an encrypted format and wherein authentication information comprises an encrypted cookie.

10. The method of claim 9, further comprising sharing a sign-out operation among two or more software applications, wherein the software applications have one or more secured features comprising:

receiving a request to sign-out of a software application when in a signed-in state;

sending a message indicating a sign-out has occurred to the other running software applications;

detecting whether authentication information is stored in a memory for the software application requesting sign-out;

in response to authentication information being stored, removing the authentication information from the memory for the software application; and

transitioning each running software application from a signed-in state to a signed-out state.

11. The method of claim 10, wherein the software applications are authorized to share the sign-in operation, further comprising:

in response to transitioning each running software application to a signed-in state, incrementing a reference count for each running software application transitioned to a signed-in state; and

in response to transitioning each running software application from a signed-in state to a signed-out state, decrementing the reference count for each running software application transitioned to a signed-out state.

12. The method of claim 11, wherein the reference count comprises the number of software applications currently in the access signed-in state or the ready signed-in state.

13. The method of claim 12, wherein the credential comprises a username and a password.

14. The method of claim 12, wherein transitioning each running software application to a signed-out state further comprises changing an interface of each running software application to a signed-out state.

15. The method of claim 12, further comprising:

detecting if the reference count is zero; and

in response to the reference count being zero, clearing the credential from the shared memory.

16. The method of claim 15, further comprising:

receiving a request to exit a software application;

detecting whether the software application is in a signed-in state; and

in response to the software application being in a signed-in state, decrementing the reference count and exiting the software application.

17. The method of claim 16, further comprising in response to the software application not being in a signed-in state, exiting the software application.

18. A computer program product readable by a computing system and encoding instructions for executing a computer process for logging-in to a software application, wherein the software application has one or more secured features, said computer process comprising:

receiving a request to enter a logged-in state within a single software application;

verifying a credential to enter an access logged-in state within the single software application;

detecting whether one or more other software applications are open; and

in response to one or more other software applications being open, advancing the open software applications to a ready logged-in state with access to the credential.

19. The computer program product of claim 18, wherein the computer process further comprises:

receiving a request to access a secured feature within the software application when the software application is in a ready logged-in state; and

in response to the request, retrieving and transmitting the credential for validation; and

in response to the credential being validated, receiving and storing authentication information and advancing the software application from the ready logged-in state to the access logged-in state.

20. The computer program product of claim 18, wherein verifying a credential comprises:

receiving a credential;

detecting whether the credential is valid;

in response to the credential being valid, writing the credential to a shared memory; and

sending a message indicating an access login has occurred to the other open software applications.

21. The computer program product of claim 20, wherein the computer process further comprises:

detecting whether one or more other software applications are starting; and

in response to one or more other software applications starting, advancing each starting software application to a ready logged-in state with access to the credential.

22. The computer program product of claim 21, wherein advancing the starting applications to a ready logged-in state comprises:

detecting whether the credential is stored in the shared memory;

in response to the credential being stored, changing an interface of each starting software application to a logged-in state; and

incrementing a reference count for each starting software application advanced to the ready logged-in state.

23. The computer program product of claim 22, wherein advancing the other open applications to the ready logged-in state comprises:

receiving the message indicating the access login has occurred;

changing an interface of the open application to a logged-in state; and

incrementing the reference count for each open application advanced to the ready logged-in state.

24. The computer program product of claim 23, wherein the reference count comprises the number of software applications presently in a logged-in state.

25. The computer program product of claim 22, wherein the credential is stored and transmitted in an encrypted format.

26. The computer program product of claim 23, further comprising sharing a logout operation between two or more software applications, wherein the software applications have one or more secured features comprising:

receiving a request to logout of a software application when in the logged-in state;

detecting whether authentication information is stored in a memory for the software application;

in response to authentication information being store, removing the authentication information from the memory for the software application;

sending a message indicating a shared logout has occurred to the other open software applications; and

advancing each software application to a logged-out state.

27. The computer program product of claim 26, wherein the software applications are approved to share the login and logout operations, further comprising:

in response to advancing each open software application to a logged-in state, incrementing a reference count for each open software application advanced to a logged-in state; and

in response to advancing each software application to a logged-out state, decrementing the reference count for each software application advanced to a logged-out state.

28. A system for logging-in to two or more software applications, wherein the software applications have one or more secured features, comprising:

a memory unit storing a shared credential; and

a processing unit receiving a request to login within a software application, processing a credential to enter an access logged-in state within the software application, detecting whether one or more other software applications are in run mode, and in response to one or more other software applications being in run mode, transitioning the software applications in run mode to a ready logged-in state with access to the credential.

29. The system of claim 28, further comprising:

a display unit to indicate the logged-in state and network activity.

30. A system for sharing a sign-in operation among two or more applications, each application having at least one secured feature, the system comprising:

a receipt module receiving a request to sign-in to a first running software application having a secured feature;

a credential module validating a sign-in input for the first running software application and changing the state of the first running software application to an access signed-in state indicating access to a secured feature; and

a transition module responsive to the credential module changing the state of a second running software application having a secure feature to a ready signed-in state with access to the sign-in input.

31. The system of claim 30, further comprising:

a memory unit storing a shared credential in a shared memory; and

a processing unit receiving a request to access a secured feature within a software application when the software application is in the ready signed-in state, in response to receiving the request, retrieving the shared credential from the shared memory, detecting whether the credential is authentic, and in response to the credential being authentic, receiving and storing authentication information for accessing the secured feature of the software application whereby the software application is transitioned from the ready signed-in state to the access signed-in state and the secured feature is accessed.

32. The system of claim 31, further comprising a sign-out module responsive to a sign-out request changing the state of the running applications to a signed-out state.