Single sign-on for unmanaged mobile devices

• US 10,171,448 B2
• Filed: 06/15/2015
• Issued: 01/01/2019
• Est. Priority Date: 06/15/2015
• Status: Active Grant

• Current Assignee: Omnissa, LLC
• Original Assignee: AirWatch LLC (Broadcom, Inc.)
• Inventors: Rykowski, Adam, Jain, Ashish, Olds, Dale Robert, Xu, Emily Hong, Barday, Kabir, Austin, Kyle, Kommireddy, Sridhara Babu
• Primary Examiner(s): Feild, Lynn D
• Assistant Examiner(s): McCoy, Richard A
• Application Number:
  US14/739,983
• Publication Number:
  US 20160366122A1
• Time in Patent Office: 1,296 Days
• Field of Search: None
• CPC Class Codes: G06F 21/41 where a single sign-on provides access to a plurality of computers
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04W 12/062 Pre-authentication

Abstract

Disclosed are various examples for providing a single sign-on experience for mobile devices that may or may not be managed. A service provider receives an access request from a first client application executed in a client device. The service provider causes the first client application, using a redirection response that redirects the access request to an identity provider, to request an authentication token from a second client application executed in the client device. The service provider receives the authentication token from the first client application. The service provider then authenticates the first client application in response to verifying the authentication token.

Claims

1. A non-transitory computer-readable medium embodying a program executable in at least one computing device, the program, when executed by the at least one computing device, being configured to cause the at least one computing device to at least:

cause a mapping between a predefined scheme name and an authentication application to be registered with a client device;

receive an access request from a client application executed in the client device;

cause the client application, using a redirection response that redirects the access request to an identity provider, to request an identity assertion from the authentication application executed in the client device, the identity assertion being requested by the client application using a local uniform resource locator (URL) beginning with the predefined scheme name that is registered with the client device to correspond to the authentication application;

receive the identity assertion from the client application;

verify the identity assertion; and

authenticate the client application.

2. The non-transitory computer-readable medium of claim 1, wherein the program, when executed by the at least one computing device, is further configured to cause the at least one computing device to:

generate a session token in response to authenticating the client application; and

set a cookie with the client application, the cookie including the session token.

3. The non-transitory computer-readable medium of claim 1, wherein the redirection response redirects the client application to the local URL.

4. The non-transitory computer-readable medium of claim 1, wherein the predefined scheme name corresponds to a randomly generated unique identifier.

5. The non-transitory computer-readable medium of claim 1, wherein the access request comprises a hypertext transfer protocol (HTTP) request, and the access request is redirected by an HTTP response having a status code of 302.

6. The non-transitory computer-readable medium of claim 1, wherein the authentication application is configured to request the identity assertion from the identity provider.

7. The non-transitory computer-readable medium of claim 1, wherein the authentication application is configured to request at least one security credential from a user of the client device.

8. A system, comprising:

at least one computing device comprising a processor and a memory; and

a service provider executable by the at least one computing device, the service provider configured to cause the at least one computing device to at least;

receive an access request from a first client application executed in a client device;

cause a mapping between a predefined scheme name and a second client application to be registered with the client device;

cause the first client application, using a redirection response that redirects the access request to an identity provider, to request an authentication token from the second client application executed in the client device, the authentication token being requested by the first client application using a local uniform resource locator (URL) beginning with the predefined scheme name that is registered with the client device to correspond to the second client application;

receive the authentication token from the first client application; and

authenticate the first client application in response to verifying the authentication token.

9. The system of claim 8, wherein the local URL includes callback information to allow the second client application to call back to the first client application to return the authentication token.

10. The system of claim 8, wherein the authentication token is received with a security assertion markup language (SAML) identity assertion.

11. The system of claim 8, wherein the service provider is further configured to cause the at least one computing device to at least:

determine whether the first client application is configured to utilize a single sign-on procedure supported by the second client application; and

wherein the first client application is sent the redirection response in response to determining that the first client application is configured to use the single sign-on procedure.

12. The system of claim 8, wherein the identity provider is executable by the at least one computing device, the identity provider configured to cause the at least one computing device to at least:

receive an authentication request from the second client application;

verify the authentication request;

generate the authentication token; and

send the authentication token to the second client application.

13. The system of claim 12, wherein the authentication request includes at least one security credential received from a user by the second client application.

14. A method, comprising:

receiving, by a service provider executed in at least one computing device comprising a processor and a memory, an access request from a first client application executed in a client device;

causing, by the service provider, a mapping between a predefined scheme name and a second client application to be registered with the client device;

causing the first client application, by the service provider using a redirection response that redirects the access request to an identity provider, to request an authentication token from the second client application executed in the client device, the authentication token being requested by the first client application using a local uniform resource locator (URL) beginning with the predefined scheme name that is registered with the client device to correspond to the second client application;

receiving, by the service provider, the authentication token from the first client application; and

authenticating, by the service provider, the first client application in response to verifying the authentication token.

15. The method of claim 14, wherein the local URL includes callback information to allow the second client application to call back to the first client application to return the authentication token.

16. The method of claim 14, wherein the authentication token is received with a security assertion markup language (SAML) identity assertion.

17. The method of claim 14, further comprising:

determining, by the service provider, whether the first client application is configured to utilize a single sign-on procedure supported by the second client application; and

wherein the first client application is sent the redirection response in response to determining that the first client application is configured to use the single sign-on procedure.

18. The method of claim 14, wherein the identity provider is executable by the at least one computing device, and the method further comprises:

receiving, by the identity provider, an authentication request from the second client application;

verifying, by the identity provider, the authentication request;

generating, by the identity provider, the authentication token; and

sending, by the identity provider, the authentication token to the second client application.

19. The method of claim 18, wherein the authentication request includes at least one security credential received from a user by the second client application.

20. The method of claim 14, wherein the predefined scheme name is a randomly generated unique identifier.