Single sign-on for managed mobile devices

Patent metadata

Field	Value
Publication number	US-10812464-B2
Application number	US-201514739975-A
Country	US
Kind code	B2
Filing date	Jun 15, 2015
Priority date	Jun 15, 2015
Publication date	Oct 20, 2020
Grant date	Oct 20, 2020

Abstract

Disclosed are various examples for single-sign on by way of managed mobile devices. For example, an identity provider service can receive a request for an identity assertion from an application executed in a client device. The identity provider service can then detect a platform associated with the client device. A response to the request can be sent based at least in part on the platform, where the response requests authentication by a management credential. Data generated by the management credential is received from the client device, and the management credential is determined to be valid for the identity assertion. The identity assertion is then sent to the client device in response to determining that the management credential is valid for the identity assertion.

First claim

The invention claimed is:

1. A non-transitory computer-readable medium embodying a program executable in a server computing device, the program, when executed by the server computing device, being configured to cause the server computing device to at least:
receive a request for an identity assertion from an application executed in a mobile device;
detect that the mobile device is associated with a specific platform of a plurality of platforms;
identify a specific platform adapter corresponding to the specific platform, the specific platform adapter being associated with a type of device management credential, the type of device management credential being a secure certificate or a Kerberos profile;
send, by the specific platform adapter, to the mobile device a response to the request requesting a device management credential corresponding to the type of device management credential, the response further requesting that the mobile device request authentication using the device management credential, the device management credential being used by a device management application that is executed in the mobile device and manages the application;
receive, by the specific platform adapter, the requested authentication request including the device management credential from the mobile device;
determine, by the specific platform adapter, that the device management credential is valid for the identity assertion; and
send the identity assertion to the mobile device in response to determining that the device management credential is valid for the identity assertion.

2. The non-transitory computer-readable medium of claim 1 , wherein the mobile device has access to the device management credential in response to authentication by a device management service of a user of the mobile device.

3. The non-transitory computer-readable medium of claim 1 , wherein, when the specific platform is iOS, the request is generated by an iOS-specific certificate adapter.

4. The non-transitory computer-readable medium of claim 1 , wherein, when the specific platform is ANDROID, the request is generated by a certificate adapter.

5. The non-transitory computer-readable medium of claim 1 , wherein the program, when executed by the server computing device, is further configured to cause the server computing device to at least:
receive a second request for a second identity assertion from a second application executed in the mobile device;
send, by the specific platform adapter, to the mobile device a second response to the second request requesting the device management credential based at least in part on the specific platform, the second response further requesting that the mobile device request authentication a second time using device management credential;
receive, by the specific platform adapter, the requested authentication request for the second time including the device management credential from the mobile device;
determine, by the specific platform adapter, that the device management credential is valid for the second identity assertion; and
send the second identity assertion to the mobile device in response to determining that the device management credential is valid for the second identity assertion.

6. A system, comprising:
at least one computing device; and
an identity provider service executable by the at least one computing device, the identity provider service configured to cause the at least one computing device to at least:
receive a request for an identity assertion from an application executed in a mobile device, the request including a user-agent string;
determine that the application corresponds to a webview of a native application rather than a browser by examining the user-agent string;
detect that the mobile device is associated with a specific platform of a plurality of platforms;
identify a specific platform adapter corresponding to the specific platform, the specific platform adapter being associated with a type of device management credential, the type of device management credential being a secure certificate or a Kerberos profile;
send, by the specific platform adapter, to the mobile device a response to the request requesting a device management credential corresponding to the type of device management credential, the response further requesting that the mobile device request authentication using the device management credential, the device management credential being used by a device management application that is executed in the mobile device and manages the application, the device management credential being a secure certificate or a Kerberos profile;
receive, by the specific platform adapter, the requested authentication request including the device management credential from the mobile device;
determine, by the specific platform adapter, that the device management credential is valid for the identity assertion; and
send the identity assertion to the mobile device in response to determining that the device management credential is valid for the identity assertion.

7. The system of claim 6 , wherein the mobile device has access to the device management credential in response to authentication by a device management service of a user of the mobile device.

8. The system of claim 6 , wherein the identity provider service is further configured to cause the at least one computing device to at least generate the response to the request by an iOS-specific certificate adapter.

9. The system of claim 6 , wherein the request for the identity assertion is redirected to the identity provider service from a service provider.

10. The system of claim 6 , wherein the response to the request is a hypertext transfer protocol (HTTP) response having a 401 authentication required status code.

11. A method, comprising:
receiving a request for an identity assertion from an application executed in a client device;
detecting that the client device is associated with a specific platform of a plurality of platforms;
identifying a specific platform adapter corresponding to the specific platform, the specific platform adapter being associated with a type of device management credential;
sending, by the specific platform adapter, to the client device a response to the request requesting a device management credential corresponding to the type of device management credential, the response further requesting that the client device request authentication using the device management credential, the device management credential being a secure certificate or a Kerberos profile, the device management credential being used by a device management application that is executed in the client device and manages the application;
receiving, by the specific platform adapter, the requested authentication request including the device management credential from the client device;
determining, by the specific platform adapter, that the device management credential is valid for the identity assertion; and
sending the identity assertion to the client device in response to determining that the device management credential is valid for the identity assertion.

12. The method of claim 11 , wherein the client device has access to the device management credential in response to authentication by a device management service of a user of the client device.

13. The method of claim 11 , wherein the request for the identity assertion is redirected from a service provider.

14. The method of claim 11 , further comprising detecting that the client device complies with a set of access rules.

15. The method of claim 11 , further comprising, in res

Assignees

• Airwatch Llc

Inventors

• Rykowski Adam
• Jain Ashish
• Olds Dale Robert
• Xu Emily Hong
• Barday Kabir
• Austin Kyle
• Kommireddy Sridhara Babu
• Brannon Jonathan Blake
• Lotero Camilo

Classifications

• H04W12/37

  Managing security policies for mobile devices or for controlling mobile applications · CPC title

• H04W12/069

  using certificates or pre-shared keys · CPC title

• H04W12/062

  Pre-authentication · CPC title

• H04L63/0823

  using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263) · CPC title

• H04L63/08

  for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title