Mobile application, identity interface

• US 9,081,951 B2
• Filed: 05/31/2012
• Issued: 07/14/2015
• Est. Priority Date: 09/29/2011
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Sondhi, Ajay, Chu, Ching-Wen, Kim, Beomsuk, Brydon, Sean
• Primary Examiner(s): Chai, Longbit
• Application Number:
  US13/485,509
• Publication Number:
  US 20130086639A1
• Time in Patent Office: 1,139 Days
• Field of Search: 726/4
• US Class Current: 1/1
• CPC Class Codes: G06F 21/41 where a single sign-on provides access to a plurality of computers
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications

Abstract

Techniques for managing identities are provided. In some examples, identity management, authentication, authorization, and token exchange frameworks may be provided for use with mobile devices, mobile applications, cloud applications, and/or other web-based applications. For example a mobile client may request to perform one or more identity management operations associated with an account of a service provider. Based at least in part on the requested operation and/or the particular service provider, an application programming interface (API) may be utilized to generate and/or perform one or more instructions and/or method calls for managing identity information of the service provider.

Claims

1. A system, comprising:

a memory storing a plurality of instructions; and

one or more hardware processors configured to access the memory, wherein the one or more hardware processors are further configured to execute the plurality of instructions to;

receive, from a mobile client application of a mobile device, an access request requesting access to an access management service provider, the access request formatted as a representational state transfer (REST) call;

determine, based at least in part on the REST call, an access management service call for accessing an access management service corresponding to the access management service provider;

determine a format for providing the access management service call based on a Lightweight Directory Access Protocol (LDAP) schema associated with the access management service provider;

perform the access management service call in accordance with the determined format, the access management service call including a token request specified in the determined format for accessing the access management service provider, the token request including a mobile client token and a user token;

receive an access token for accessing the access management service provider based at least in part on the mobile client token and the user token; and

cause the mobile client application to perform a function associated with the access management service provider based on the received access token upon authentication of a user of the mobile client application.

2. The system of claim 1, wherein the client application comprises a software as a service (SaaS) application, or a Rich Internet Application (RIA).

3. The system of claim 1, wherein the access request comprises an authentication request, an authorization request, a user profile management request, a policy management request, or a password management request.

4. The system of claim 3, wherein the authentication request includes a user identifier (ID) associated with the user of the mobile client application, a password associated with the user of the mobile client application, and the mobile client token for indicating that the mobile client application is authenticated, the user ID and the password for authenticating the user with the access management service.

5. The system of claim 1, wherein the access management service call comprises a method call to implement a token exchange.

6. The system of claim 1, wherein the access request further includes an indication of the access management service provider for which access is requested, wherein the mobile client token indicates that the mobile client application is authenticated and the user token indicates that the user of the mobile client application is authenticated.

7. The system of claim 6, wherein the one or more hardware processors are further configured to provide the access token to the mobile client application at least in response to receiving an indication that the user and the client application are granted access to the access management service provider by the access management service.

8. The system of claim 1, wherein a first access management service call corresponding to a first service provider is different from a second access management service call corresponding to a second service provider.

9. The system of claim 1, wherein the access management service to be used is specified by the access management service provider and not indicated to the client application.

10. A computer-implemented method, comprising:

receiving, by a computer system, a representational state transfer (REST) interface access request for accessing a third-party server, the REST interface access request received from a mobile client application;

determining, by the computer system, an access management service call corresponding to the third-party server for which access is requested, the determining based at least in part on the REST interface access request received from the mobile client application;

determining, by the computer system, a format for providing the access management service call based on a Lightweight Directory Access Protocol (LDAP) schema associated with the access management service provider;

providing, by the computer system, the access management service call in accordance with the determined format to an access management service associated with the third-party server for which access is requested, the access management service call including a token request specified in the determined format for accessing the third-party server, the token request including a mobile client token and a user token;

receiving, by the computer system, an access token for accessing the third-party server based at least in part on the mobile client token and the user token;

providing, by the computer system, the access token to the mobile client application; and

causing the mobile client application to perform a function associated with the access management service provider based on the received access token upon authentication of a user of the mobile client application.

11. The computer-implemented method of claim 10, wherein the client application comprises a rich Internet application, or a software as a service application.

12. The computer-implemented method of claim 10, wherein the request to access the third-party server is received as a REST call independent of an application programming interface (API) of the third-party server for which access is requested.

13. The computer-implemented method of claim 10, further comprising determining, based at least in part on an application programming interface (API) of the third-party server, a predefined manner for providing the token request.

14. A computer-readable memory storing a plurality of instructions executable by one or more hardware processors, the plurality of instructions comprising:

instructions that cause the one or more hardware processors to receive, from a mobile client application, a representational state transfer (REST) interface call for requesting access to a service provider;

instructions that cause the one or more hardware processors to determine, based at least in part on the REST interface call from the mobile client application, a method call for utilizing an access management service associated with the service provider;

instructions that cause the one or more hardware processors to determine a format for providing the method call based on a Lightweight Directory Access Protocol (LDAP) schema associated with the service provider;

instructions that cause the one or more hardware processors to transmit, to the access management service associated with the service provider, the method call for utilizing the access management service in accordance with the determined format, the method call including a token request specified in the determined format for accessing the service provider, the token request including a mobile client token and a user token;

instructions that cause the one or more hardware processors to receive, from the access management service, an access decision based on the mobile client token and the user token; and

instructions that cause the one or more hardware processors to provide, based at least in part on the access decision, an access token to the mobile client application so that the mobile client application can perform a function associated with the access management service provider based on the received access token upon authentication of a user of the mobile client application.

15. The computer-readable memory of claim 14, wherein the REST interface call for requesting access to the service provider includes at least a request to authenticate the user of the mobile client application.

16. The computer-readable memory of claim 14, further comprising instructions that cause the one or more hardware processors to determine the format for transmission of the method call based at least in part on an application programming interface (API) of the access management service.

17. The computer-readable memory of claim 16, wherein a first format of a method call for a first access management service is different from a second format of a method call for a second access management service.

18. The computer-readable memory of claim 14, wherein the access management service is configured to receive method calls other than REST interface calls.

19. The computer-readable memory of claim 14, wherein the method call comprises a request to authenticate the user of the mobile client application, a request to authorize the user of the mobile client application, or a request to perform a token exchange for providing user access to the service provider.