Peer Applications Trust Center

• US 20150195271A1
• Filed: 03/23/2015
• Published: 07/09/2015
• Est. Priority Date: 04/17/2012
• Status: Active Grant

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Yu, Loc An
• Granted Patent: US 9,853,960 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 21/51 at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
• CPC Class Codes: G06F 2221/033 Test or assess software
• CPC Class Codes: H04L 63/00 Network architectures or network communication protocols for network security cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00; network architectures or network communication protocols for wireless network security H04W12/00; security arrangements for protecting computers or computer systems against unauthorised activity G06F21/00
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• 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/10 for controlling access to devices or network resources

Abstract

Concepts and technologies are disclosed herein for a peer applications trust center. A trust client can execute on a client computer and a trust service can execute on a server computer to provide the peer applications trust center. The trust client or trust server can register applications. During registration, the trust server or the trust client can generate a public key or other identifier for identifying the registered application. If another application requests access to the registered application, the trust server or the trust client can determine if the request specifies a registered application by name. If the requestor is granted access to the application, the requestor can be issued a token. Tokens can be revoked, updated, replaced, or renewed for various purposes.

Claims

1. A method comprising:

receiving, at a processor executing a trust service, a request to establish a trust relationship between a second application and a first application, the request being received from the second application;

determining, by the processor, that the trust relationship is authorized;

generating, by the processor, a unique identifier that identifies the first application;

issuing, by the processor, a token to the second application;

receiving, by the processor and from the second application, an application access request comprising the unique identifier and the token, wherein the processor identifies the first application based upon the unique identifier; and

establishing, by the processor, the trust relationship between the first application and the second application whereby the first application has access to the second application.

2. The method of claim 1, further comprising determining that the application access request is to be granted by authenticating the second application based upon the token.

3. The method of claim 1, further comprising:

determining that the trust relationship is authorized based upon information included in the request to establish the trust relationship.

4. The method of claim 1, further comprising determining that the application access request is to be granted based upon the unique identifier.

5. The method of claim 1, wherein the request to establish the trust relationship comprises a name identifying an application.

6. The method of claim 5, wherein determining that the trust relationship is authorized comprises:

determining that the name corresponds to the first application; and

determining that the first application comprises a registered application.

7. The method of claim 1, wherein issuing the token comprises:

determining a time period for which the token will be valid;

specifying a life of the token, the life of the token corresponding to the time period; and

issuing the token with the life specified.

8. The method of claim 7, further comprising:

determining that the token has expired;

issuing a new token; and

reestablishing the trust relationship using the new token.

9. The method of claim 1, further comprising:

determining that a new version of the token is available;

revoking the token;

issuing the new version of the token; and

reestablishing the trust relationship using the new version of the token.

10. The method of claim 1, wherein the first application is executed by a first application server, and wherein the second application is executed by a second application server.

11. A system comprising:

a processor; and

a memory that stores computer-executable instructions that, when executed by the processor, cause the processor to perform operations comprising;

receiving a request to establish a trust relationship between a first application and a second application, the request being received from the second application,

determining that the trust relationship is authorized,

generating a unique identifier that identifies the first application,

issuing a token to the second application,

receiving, from the second application, an application access request comprising the unique identifier and the token, wherein the processor identifies the first application based upon the unique identifier, and

establishing the trust relationship between the first application and the second application whereby the first application has access to the second application.

12. The system of claim 11, wherein the computer-executable instructions, when executed by the processor, cause the processor to perform operations further comprising:

determining that the application access request is to be granted by authenticating the second application based upon the token.

13. The system of claim 11, wherein the request to establish the trust relationship comprises a name identifying an application, and wherein determining that the trust relationship is authorized comprises determining that the name corresponds to the first application and determining that the first application comprises a registered application.

14. The system of claim 11, wherein the computer-executable instructions, when executed by the processor, cause the processor to perform operations further comprising:

determining a time period for which the token will be valid;

specifying a life of the token, the life of the token corresponding to the time period;

issuing the token with the life specified;

determining that the token has expired;

issuing a new token; and

reestablishing the trust relationship using the new token.

15. The system of claim 11, wherein the computer-executable instructions, when executed by the processor, cause the processor to perform operations further comprising:

determining that a new version of the token is available;

revoking the token;

issuing the new version of the token; and

reestablishing the trust relationship using the new version of the token.

16. A computer storage medium having computer-executable instructions stored thereon that, when executed by a processor, cause the processor to execute a method comprising:

receiving a request to establish a trust relationship between a first application and a second application, the request being received from the second application,

determining that the trust relationship is authorized,

generating a unique identifier that identifies the first application, issuing a token to the second application,

receiving, from the second application, an application access request comprising the unique identifier and the token, wherein the processor identifies the first application based upon the unique identifier, and

establishing the trust relationship between the first application and the second application whereby the first application has access to the second application.

17. The computer storage medium of claim 16, wherein the computer-executable instructions, when executed by the processor, cause the processor to perform operations further comprising:

determining that the application access request is to be granted by authenticating the second application based upon the token.

18. The computer storage medium of claim 16, wherein the computer-executable instructions, when executed by the processor, cause the processor to perform operations further comprising:

determining that a new version of the token is available;

revoking the token;

issuing the new version of the token; and

reestablishing the trust relationship using the new version of the token.

19. The computer storage medium of claim 16, wherein the request to establish the trust relationship comprises a name identifying an application, and wherein determining that the trust relationship is authorized comprises determining that the name corresponds to the first application and determining that the first application comprises a registered application.

20. The computer storage medium of claim 16, wherein the computer-executable instructions, when executed by the processor, cause the processor to perform operations further comprising:

determining a time period for which the token will be valid;

specifying a life of the token, the life of the token corresponding to the time period;

issuing the token with the life specified;

determining that the token has expired;

issuing a new token; and

reestablishing the trust relationship using the new token.