User impersonation/delegation in a token-based authentication system

• US 9,497,184 B2
• Filed: 03/28/2011
• Issued: 11/15/2016
• Est. Priority Date: 03/28/2011
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Fork, Michael John, Price, Vincent Edmund
• Primary Examiner(s): Revak, Christopher
• Assistant Examiner(s): Savenkov, Vadim
• Application Number:
  US13/072,884
• Publication Number:
  US 20120254957A1
• Time in Patent Office: 2,059 Days
• Field of Search: 726/6, 726 2- 5, 726 7- 10, 713155-159, 713168-181
• US Class Current: 1/1
• CPC Class Codes: G06F 21/33 using certificates
• CPC Class Codes: G06F 2221/2115 Third party
• 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/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0884 by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
• CPC Class Codes: H04L 9/3213 using tickets or tokens, e.g. Kerberos network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

Abstract

A “trusted service” establishes a trust relationship with an identity provider and interacts with the identity provider over a trusted connection. The trusted service acquires a token from the identity provider for a given user (or set of users) without having to present the user'"'"'s credentials. The trusted service then uses this token (e.g., directly, by invoking an API, by acquiring another token, or the like) to access and obtain a cloud service on a user'"'"'s behalf even in the user'"'"'s absence. This approach enables background services to perform operations within a hosted session (e.g., via OAuth-based APIs) without presenting user credentials or even having the user present.

Claims

1. A method, operating within a service, of enabling access by the service to an application executing in a computing entity, comprising:

establishing, by the service, a trust relationship between the service and an identity provider by which the service becomes a trusted service;

requesting, by the trusted service, a token from the identity provider;

receiving, by the trusted service, the token from the identity provider, the token having been generated by the identity provider without requiring presentation by the trusted service of user credential information;

the trusted service, on behalf of a user, using the token and a user credential to establish the trusted service as an authenticated user to the application; and

upon establishing the trusted service as an authenticated user, the trusted service accessing the application.

2. The method as described in claim 1 wherein the token is used to establish the trusted service as an authenticated user by the trusted service forwarding the token to a service provider associated with the identity provider and, upon a validation, the trusted service receiving authentication session information, the authentication session information indicating that the trusted service is an authenticated user for a session.

3. The method as described in claim 2 wherein the token received by the trusted service is a generic token for a set of authorized users.

4. The method as described in claim 3 wherein the validation checks to determine that the user credential is associated with the generic token.

5. The method as described in claim 2 wherein the token received by the trusted service is a specific token for an authorized user.

6. The method as described in claim 5 wherein the validation identifies a username associated with the specific token and verifies that the username matches the user credential.

7. The method as described in claim 2 wherein the validation is performed at least in part by the identity provider.

8. The method as described in claim 1 wherein the computing entity is a shared pool of configurable computing resources.

9. The method as described in claim 1 wherein the trusted service accesses the application using an OAuth-based application programming interface (API).

10. The method as described in claim 1 wherein the service is associated with an on-premises application and the application executing in the computing entity is a cloud-based service.

11. The method as described in claim 1 wherein, for a particular trusted connection between the trusted service and the identity provider, the token represents a trusted service-configured subset of a set of target users.

12. The method as described in claim 1 further including scoping the token as a function of one or more of a set of attributes, the attributes being one of:

time, location, status and role.

13. Apparatus, comprising:

a processor;

computer memory holding computer program instructions that when executed by the processor perform a method, operating within a service, of enabling access by the service to an application executing in a computing entity, the method comprising;

establishing, by the service, a trust relationship between the service and an identity provider by which the service becomes a trusted service;

requesting, by the trusted service, a token from the identity provider;

receiving, by the trusted service, the token from the identity provider, the token having been generated by the identity provider without requiring presentation by the trusted service of user credential information;

the trusted service, on behalf of a user, using the token and a user credential to obtain an authenticated user identity for the trusted service and by which the user can be impersonated to the application; and

upon receiving the authenticated user identity establishing the trusted service as an authenticated user, the trusted service accessing the application.

14. The apparatus as described in claim 13 wherein the token is used by the trusted service forwarding the token to a service provider associated with the identity provider and, upon a validation, the trusted service receiving the authenticated user identity.

15. The apparatus as described in claim 14 wherein the token received by the trusted service is a generic token for a set of authorized users.

16. The apparatus as described in claim 15 wherein the validation checks to determine that the user credential is associated with the generic token.

17. The apparatus as described in claim 14 wherein the token received by the trusted service is a specific token for an authorized user.

18. The apparatus as described in claim 17 wherein the validation identifies a username associated with the specific token and verifies that the username matches the user credential.

19. A computer program product in a non-transitory computer readable medium for use in a data processing system, the computer program product holding computer program instructions which, when executed by the data processing system, perform a method, operating within a service, of enabling access by the service to an application executing in a computing entity, the method comprising:

establishing, by the service, a trust relationship with an identity provider by which the service becomes a trusted service;

requesting, by the trusted service, a token from the identity provider;

receiving, by the trusted service, the token from the identity provider, the token having been generated by the identity provider;

receiving, by the trusted service, the token from the identity provider, the token having been generated by the identity provider without presentation by the trusted service of user credential information;

the trusted service, on behalf of a user, using the token and a user credential to obtain an authenticated user identity for the trusted service and by which the user can be impersonated to the application; and

upon receiving the authenticated user identity establishing the trusted service as an authenticated user, the trusted service accessing the application.

20. The computer program product as described in claim 19 wherein the token is used by the trusted service forwarding the token to a service provider associated with the identity provider and, upon a validation, the trusted service receiving the authenticated user identity.

21. The computer program product as described in claim 20 wherein the token received by the trusted service is a generic token for a set of authorized users.

22. The computer program product as described in claim 21 wherein the validation checks to determine that the user credential is associated with the generic token.

23. The computer program product as described in 20 wherein the token received by the trusted service is a specific token for an authorized user.

24. The computer program product as described in claim 23 wherein the validation identifies a username associated with the specific token and verifies that the username matches the user credential.