# US 2013/0160099 A1 · Token based security protocol for managing access to web services

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

- Number: US 2013/0160099 A1
- Document ID: US20130160099A1
- Status: Published application
- Kind: A1
- Application number: 13/326,119
- Filed: 2011-12-14
- Published: 2013-06-20
- Earliest claimed: 2011-12-14
- Assignees: Cellco Partnership d/b/a Verizon Wireless
- Inventors: Kenneth Leroy FITZPATRICK, III
- Web page: https://patentgrep.com/patent/US20130160099A1

## CPC

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

## Abstract

Token based techniques for managing client access to individual methods or resources provided by an application or service can be implemented at the application server hosting the application or service. Such techniques include performing client authentication and authorization based on information associated with the client as specified in a security token generated for the client. The security token associated with the client enables a service provider to monitor and control client access to the methods of the service on an individual basis.

## Claims

### Claim 1

A method, comprising:
at a server hosting a web service, receiving through a communication network from a client executing at a user device, a request message requesting access to a particular function from among a plurality of functions offered by the web service, the request message including a function identifier identifying the particular function and further including a security token associated with the client;
validating the security token based on token validation information included within the security token and the function identifier, the security token being associated with one or more functions from the plurality of functions offered by the web service;
extracting authentication information for the client from the security token;
authenticating the client based on the authentication information extracted from the security token for the client;
upon successfully validating the security token based on the token validation information and the function identifier and upon successfully authenticating the client in accordance with the authentication information extracted from the security token, processing the request message from the client so as to make the particular function as identified by the function identifier in the request message accessible to the client through the communication network; and
sending a response message through the communication network from the server to the client at the user device based on the processing of the request message and the validation of the security token and the authentication of the client.

### Claim 2 (depends on 1)

The method of claim 1, wherein the token validation information extracted from the security token includes one or more of a token version number, a token expiration date, or a source communication address modifier flag.

### Claim 3 (depends on 1)

The method of claim 1, wherein:
the request message is a Hyper-Text Transfer Protocol (HTTP) message comprising a Simple Object Access Protocol (SOAP) message;
the SOAP message includes a message header and a message body;
the message header of the SOAP message includes the security token; and
the message body of the SOAP message includes the function identifier identifying the particular function.

### Claim 4 (depends on 1)

The method of claim 1, wherein the validating of the security token comprises:
querying a database for an access list associated with the security token, the access list comprising a list of function identifiers corresponding to one or more of the plurality of functions offered by the web service;
determining whether the function identifier in the request message is specified in the access list for the security token; and
successfully validating the security token based on the determination, when the function identifier in the request message is specified in the access list for the security token.

### Claim 5 (depends on 4)

The method of claim 4, wherein the security token includes a cryptographically random value, and the cryptographically random value is used as a unique identifier for the security token in the database.

### Claim 6 (depends on 1)

The method of claim 1, wherein the authenticating comprises:
determining whether the client authentication information extracted from the security token specifies an authentication type for the client;
upon determining that the client authentication information specifies the authentication type for the client, acquiring an authentication parameter corresponding to the authentication type specified for the client; and
authenticating the client based on the acquired authentication parameter.

### Claim 7 (depends on 6)

The method of claim 6, wherein the authentication type is at least one of a client domain name or a client user identifier.

### Claim 8 (depends on 6)

The method of claim 6, wherein the authentication parameter is acquired from an operating system on the user device of the client.

### Claim 9 (depends on 6)

The method of claim 6, wherein the authentication parameter is acquired from the communication network.

### Claim 10 (depends on 6)

The method of claim 6, wherein the authentication of the client based on the security token associated with the client enables the server hosting the web service to track or limit the client's access to the plurality of functions offered by the web service on an individual basis rather than permitting or restricting access to the web service and the plurality of functions as a whole.

### Claim 11 (depends on 1)

The method of claim 1, wherein a first portion of the security token received in the request message is encoded with a token header.

### Claim 12 (depends on 11)

The method of claim 11, wherein a second portion of the security token received in the request message is encoded with a cryptographically random value.

### Claim 13 (depends on 11)

The method of claim 11, wherein the token header encoded in the first portion of the security token includes the token validation information and the authentication information for the client.

### Claim 14

An application server, comprising:
a network communication device configured to exchange data communications through a communication network, the communication network including at least one database accessible to the network communication device;
a processor coupled to the network communication device;
a storage device accessible to the processor; and
an application program in the storage device, the application program including a plurality of functions of a web service, wherein execution of the application program by the processor configures the application server to exchange data communications related to the plurality of functions of the web service with an associated client of a user device through the communication network,
wherein the processor is configured to perform functions including:
a message handling function to receive through a communication network from a client executing at a user device, a request message requesting access to one of the functions of the web service, the request message including a function identifier identifying the one function of the web service and further including a security token associated with the client;
a token validation function to validate the security token based on token validation information included within the security token and the function identifier, the security token being associated with one or more functions of the functions of the web service;
a client information extraction function to extract authentication information for the client from the security token;
a client authentication function to authenticate the client based on the authentication information extracted from the security token;
a request processing function to process the request message from the client so as to make the one function of the web service as identified by the function identifier in the request message accessible to the client through the communication network, when the security token is validated via the token validation function and when the client is authenticated via the client authentication function; and
a response communication function to transmit a response message through the communication network to the client at the user device based on the processing of the request message.

### Claim 15

An article of manufacture, comprising a non-transitory computer-readable medium and computer-executable instructions embodied in the medium that, if executed by a computing device, cause the computing device to perform functions including functions to:
receive through a communication network from a client executing at a user device, a request message requesting access to a particular function from among a plurality of functions offered by a web service hosted at the computing device, the request message including a function identifier identifying the particular function and further including a security token associated with the client;
validate the security token based on token validation information included within the security token and the function identifier, the security token being associated with one or more functions from the plurality of functions offered by the web service;
extract authentication information for the client from the security token;
authenticate the client based on the authentication information extracted from the security token for the client;
process the request message from the client so as to make the particular function as identified by the function identifier in the request message accessible to the client through the communication network, when the token is validated based on the token validation information and the function identifier and when the client is authenticated based on the authentication information; and
transmit a response message through the communication network from the server to the client at the user device based on the processing of the request message and the validation of the security token and the authentication of the client.

### Claim 16 (depends on 15)

The article of claim 15, wherein the token validation information extracted from the security token includes one or more of a token version number, a token expiration date, or a source communication address modifier flag.

### Claim 17 (depends on 15)

The article of claim 15, wherein:
the request message is a Hyper-Text Transfer Protocol (HTTP) message comprises a Simple Object Access Protocol (SOAP) message;
the SOAP message includes a message header and a message body;
the message header of the SOAP message includes the security token; and
the message body of the SOAP message includes the function identifier identifying the particular function.

### Claim 18 (depends on 15)

The article of claim 15, wherein the function to authenticate the client includes functions to:
determine whether the client authentication information extracted from the security token specifies an authentication type for the client;
acquire an authentication parameter corresponding to the authentication type specified for the client, if it is determined that the extracted client authentication information specifies the authentication type for the client; and
authenticate the client based on the acquired authentication parameter.

### Claim 19 (depends on 18)

The article of claim 18, wherein the authentication type is at least one of a client domain name or a client user identifier.

### Claim 20 (depends on 18)

The article of claim 18, wherein the authentication parameter is acquired from an operating system on the user device of the client.

### Claim 21 (depends on 18)

The article of claim 18, wherein the authentication parameter is acquired from the communication network.

### Claim 22 (depends on 15)

The article of claim 15, wherein a first portion of the security token received in the request message is encoded with a token header.

### Claim 23 (depends on 22)

The article of claim 22, wherein a second portion of the security token received in the request message is encoded with a cryptographically random value.
