# US 2017/0251367 A1 · Authenticating mobile applications using policy files

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

- Number: US 2017/0251367 A1
- Document ID: US20170251367A1
- Status: Published application
- Kind: A1
- Application number: 15/592,395
- Filed: 2017-05-11
- Published: 2017-08-31
- Earliest claimed: 2014-12-04
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Ishai Borovoy; Iddo Levin; Haim Schneider; Gal Shachor; Artem Spector
- Web page: https://patentgrep.com/patent/US20170251367A1

## CPC

- H04W 12/06: Authentication
- G06F 21/33: using certificates
- G06F 21/44: Program or device authentication
- H04L 12/06: Answer-back mechanisms or circuits
- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- H04L 63/062: {for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- 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 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- G06F 2221/2103: Challenge-response
- H04L 63/0815: {providing single-sign-on or federations}
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- 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

Examples of techniques for authenticating mobile applications are described herein. A method can include receiving, by a processor, a key pair and a policy file associated with a mobile service. The processor can receive a service request from a mobile application at a security gateway. The processor can detect that the service request includes an invalid or missing access token. The processor can redirect the mobile application to request a grant token from an authorization end point on a server. The processor can receive a grant token request from the mobile application and forward the grant token request to the server based on a policy file, the policy file including a list of: a plurality of security objects to be authenticated, a plurality of computing devices to authenticate the security objects, and an order of authentication.

## Claims

### Claim 1

A method, comprising:
receiving, by a processor, a key pair and a policy file associated with a mobile service;
receiving, by the processor, a service request from a mobile application at a security gateway;
detecting, by the processor, the service request comprising an invalid or missing access token;
redirecting, by the processor, the mobile application to request a grant token from an authorization end point on a server; and
receiving, by the processor, a grant token request from the mobile application and forwarding the grant token request to the server based on a policy file, the policy file comprising a list of: a plurality of security objects to be authenticated, a plurality of computing devices to authenticate the security objects, and an order of authentication.

### Claim 2 (depends on 1)

The method of claim 1, further comprising sending an authentication challenge to the mobile application with a response based on the policy file.

### Claim 3 (depends on 2)

The method of claim 2, wherein the authentication challenge comprises a user authentication challenge.

### Claim 4 (depends on 2)

The method of claim 2, further comprising receiving a second request from the mobile application with a correct authentication response to the authentication challenge and forwarding the second request to the server to generate a grant token.

### Claim 5 (depends on 1)

The method of claim 1, further comprising forwarding the service request to the server and returning a service response to the mobile application if the service request includes a valid access token.

### Claim 6 (depends on 1)

The method of claim 1, wherein the access token comprises:
a user authentication scope, a device authentication scope, and an application authenticity scope;
a device identification number; and
a user identification.

### Claim 7

A system, comprising a processor to:
receive a key pair and a policy file associated with a mobile service;
receive a service request from a mobile application at a security gateway;
detect the service request comprising an invalid or missing access token;
redirect the mobile application to request a grant token from an authorization end point on a server; and
receive a grant token request from the mobile application and forward the grant token request to the server based on a policy file, the policy file comprising a list of: a plurality of security objects to be authenticated, a plurality of computing devices to authenticate the security objects, and an order of authentication.

### Claim 8 (depends on 7)

The system of claim 7, wherein the processor is further configured to send an authentication challenge to the mobile application with a response based on the policy file.

### Claim 9 (depends on 8)

The system of claim 8, wherein the authentication challenge comprises a user authentication challenge.

### Claim 10 (depends on 8)

The system of claim 8, wherein the processor is further configured to receive a second request from the mobile application with a correct authentication response to the authentication challenge and forward the second request to the server to generate a grant token.

### Claim 11 (depends on 7)

The system of claim 7, wherein the processor is further configured to forward the service request to the server and return a service response to the mobile application if the service request includes a valid access token.

### Claim 12 (depends on 7)

The system of claim 7, wherein the access token comprises:
a user authentication scope, a device authentication scope, and an application authenticity scope;
a device identification number; and
a user identification.

### Claim 13

A computer program product for authenticating mobile applications, the computer program product comprising a computer-readable storage medium having program code embodied therewith, wherein the computer readable storage medium is not a transitory signal per se, the program code executable by a processor to cause the processor to:
receive a key pair and a policy file associated with a mobile service;
receive a service request from a mobile application at a security gateway;
detect the service request comprising an invalid or missing access token;
redirect the mobile application to request a grant token from an authorization end point on a server; and
receive a grant token request from the mobile application and forward the grant token request to the server based on a policy file, the policy file comprising a list of: a plurality of security objects to be authenticated, a plurality of computing devices to authenticate the security objects, and an order of authentication.

### Claim 14 (depends on 13)

The computer program product of claim 13, further comprising program code executable by the processor to send an authentication challenge to the mobile application with a response based on the policy file.

### Claim 15 (depends on 14)

The computer program product of claim 14, wherein the authentication challenge comprises a user authentication challenge.

### Claim 16 (depends on 14)

The computer program product of claim 14, further comprising program code executable by the processor to receive a second request from the mobile application with a correct authentication response to the authentication challenge and forward the second request to the server to generate a grant token.

### Claim 17 (depends on 13)

The computer program product of claim 13, further comprising program code executable by the processor to forward the service request to the server and return a service response to the mobile application if the service request includes a valid access token.

### Claim 18 (depends on 13)

The computer program product of claim 13, wherein the access token comprises:
a user authentication scope, a device authentication scope, and an application authenticity scope;
a device identification number; and
a user identification.
