# US 2012/0254957 A1 · User impersonation/delegation in a token-based authentication system

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254957 A1
- Document ID: US20120254957A1
- Status: Published application
- Kind: A1
- Application number: 13/072,884
- Filed: 2011-03-28
- Published: 2012-10-04
- Earliest claimed: 2011-03-28
- Assignees: International Business Machines Corporation
- Inventors: Michael John Fork; Vincent Edmund Price
- Web page: https://patentgrep.com/patent/US20120254957A1

## CPC

- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- G06F 21/33: using certificates
- 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)}
- 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)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- G06F 2221/2115: Third party
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- 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}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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

### Claim 1

A method, operable within a trusted service, of enabling access to an application executing in a computing entity, comprising:
establishing a trust relationship with an identity provider;
requesting a token from the identity provider;
receiving the token from the identity provider, the token having been generated by the identity provider without requiring a user credential;
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, accessing the application.

### Claim 2 (depends on 1)

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

### Claim 3 (depends on 2)

The method as described in claim 2 wherein the token is a generic token for a set of authorized users.

### Claim 4 (depends on 3)

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

### Claim 5 (depends on 2)

The method as described in claim 2 wherein the token is a specific token for an authorized user.

### Claim 6 (depends on 5)

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.

### Claim 7 (depends on 2)

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

### Claim 8 (depends on 1)

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

### Claim 9 (depends on 1)

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

### Claim 10

Apparatus, comprising:
a processor;
computer memory holding computer program instructions that when executed by the processor perform a method of enabling access to an application executing in a computing entity, the method comprising:
establishing a trust relationship with an identity provider;
requesting a token from the identity provider;
receiving the token from the identity provider, the token having been generated by the identity provider without requiring a user credential;
on behalf of a user, using the token and a user credential to obtain an authenticated user identity by which the user can be impersonated to the application; and
upon receiving the authenticated user identity, accessing the application.

### Claim 11 (depends on 10)

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

### Claim 12 (depends on 11)

The apparatus as described in claim 11 wherein the token is a generic token for a set of authorized users.

### Claim 13 (depends on 12)

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

### Claim 14 (depends on 11)

The apparatus as described in claim 11 wherein the token is a specific token for an authorized user.

### Claim 15 (depends on 14)

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

### Claim 16

A computer program product in a 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 of enabling access to an application executing in a computing entity, the method comprising:
establishing a trust relationship with an identity provider;
requesting a token from the identity provider;
receiving the token from the identity provider, the token having been generated by the identity provider without requiring a user credential;
on behalf of a user, using the token and a user credential to obtain an authenticated user identity by which the user can be impersonated to the application; and
upon receiving the authenticated user identity, accessing the application.

### Claim 17 (depends on 16)

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

### Claim 18 (depends on 17)

The computer program product as described in claim 17 wherein the token is a generic token for a set of authorized users.

### Claim 19 (depends on 18)

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

### Claim 20

The computer program product as described in 17 wherein the token is a specific token for an authorized user.

### Claim 21 (depends on 20)

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

### Claim 22

An identity provider apparatus, comprising:
a processor;
computer memory holding computer program instructions executed by the processor to perform a method, comprising:
establishing a trust relationship with a trusted service over a trusted connection;
receiving from the trusted service a request for a token;
generating the token without requiring a user credential; and
returning the token to the trusted service to enable the trusted service to impersonate a user by using the token and a user credential to obtain an authenticated user identity.

### Claim 23 (depends on 22)

The identity provider apparatus as described in claim 22 wherein the method further includes, at a subsequent time, receiving the token and performing a validation.

### Claim 24 (depends on 23)

The identity provider apparatus as described in claim 23 wherein the token is a generic token for a set of authorized users and the validation checks to determine that the user credential is associated with the generic token.

### Claim 25 (depends on 23)

The identity provider apparatus as described in claim 23 wherein the token is a specific token for an authorized user, and the validation identifies a username associated with the specific token and verifies that the username matches the user credential.
