# US 2017/0289137 A1 · Server authentication using multiple authentication chains

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

- Number: US 2017/0289137 A1
- Document ID: US20170289137A1
- Status: Published application
- Kind: A1
- Application number: 15/087,486
- Filed: 2016-03-31
- Published: 2017-10-05
- Earliest claimed: 2016-03-31
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Dimitrios Pendarakis; Enriquillo Valdez
- Web page: https://patentgrep.com/patent/US20170289137A1

## CPC

- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A client seeking to establish a cryptographically-secure channel to a server has an associated public key acceptance policy. The policy specifies a required number of certificates that must be associated with the server's public key, as well as one or more conditions associated with those certificates, that must be met before the client “accepts” the server's public key. The one or more conditions typically comprise a trust function that must be satisfied before a threshold level of trust of the client is met. A representative public key acceptance policy would be that certificate chains for the public key are valid and non-overlapping with different root CAs, and that some configurable number of those chains be present. The technique may be implemented within the context of an existing client-server SSL/TLS handshake.

## Claims

### Claim 1

A method to authenticate a server to a client, the server having an associated public key, comprising:
associating “n” distinct certificates to the server's public key, each of the “n” distinct certificates being issued by a distinct certificate authority (CA);
responsive to the client initiating a request for a secure channel to the server, providing the client the “n” distinct certificates; and
responsive to receipt from the client of an indication that the public key satisfies a client public key acceptance policy, establishing the secure channel between the client and the server;
the client public key acceptance policy specifying a required number of valid, non-overlapping certificate chains that must be present to satisfy a client threshold level of trust.

### Claim 2 (depends on 1)

The method as described in claim 1 wherein each of the distinct certificates has a certification chain with a different root certificate authority.

### Claim 3 (depends on 2)

The method as described in claim 2 wherein the certificate chains for the “n” distinct certificates are valid and non-overlapping with respect to their intermediate and root CAs.

### Claim 4 (depends on 1)

The method as described in claim 1 wherein the client threshold level of trust is designated by a trust function computed over the certificate chains.

### Claim 5 (depends on 1)

The method as described in claim 1 further including requesting the “n” distinct certificates from the distinct certificate authorities.

### Claim 6 (depends on 1)

The method as described in claim 1 wherein “n” is greater than 2.

### Claim 7

An apparatus associated with a server having a public key, comprising:
a processor;
computer memory holding computer program instructions executed by the processor to authenticate the server to a client, the computer program instructions operative to:
associate “n” distinct certificates to the server's public key, each of the “n” distinct certificates being issued by a distinct certificate authority (CA);
responsive to the client initiating a request for a secure channel to the server, provide the client the “n” distinct certificates; and
responsive to receipt from the client of an indication that the public key satisfies a client public key acceptance policy, establish the secure channel between the client and the server;
the client public key acceptance policy specifying a required number of valid, non-overlapping certificate chains that must be present to satisfy a client threshold level of trust.

### Claim 8 (depends on 7)

The apparatus as described in claim 7 wherein each of the distinct certificates has a certification chain with a different root certificate authority.

### Claim 9 (depends on 8)

The apparatus as described in claim 8 wherein the certificate chains for the “n” distinct certificates are valid and non-overlapping with respect to their intermediate and root CAs.

### Claim 10 (depends on 7)

The apparatus as described in claim 7 wherein the client threshold level of trust is designated by a trust function computed over the certificate chains.

### Claim 11 (depends on 7)

The apparatus as described in claim 7 further including requesting the “n” distinct certificates from the distinct certificate authorities.

### Claim 12 (depends on 7)

The apparatus as described in claim 7 wherein “n” is greater than 2.

### Claim 13

A computer program product in a non-transitory computer readable medium for use in a data processing system associated with a server, the server having a public key, the computer program product holding computer program instructions which, when executed by the data processing system, are operative to:
associate “n” distinct certificates to the server's public key, each of the “n” distinct certificates being issued by a distinct certificate authority (CA);
responsive to the client initiating a request for a secure channel to the server, provide the client the “n” distinct certificates; and
responsive to receipt from the client of an indication that the public key satisfies a client public key acceptance policy, establish the secure channel between the client and the server;
the client public key acceptance policy specifying a required number of valid, non-overlapping certificate chains that must be present to satisfy a client threshold level of trust.

### Claim 14 (depends on 13)

The apparatus as described in claim 13 wherein each of the distinct certificates has a certification chain with a different root certificate authority.

### Claim 15 (depends on 14)

The apparatus as described in claim 14 wherein the certificate chains for the “n” distinct certificates are valid and non-overlapping with respect to their intermediate and root CAs.

### Claim 16 (depends on 13)

The apparatus as described in claim 13 wherein the client threshold level of trust is designated by a trust function computed over the certificate chains.

### Claim 17 (depends on 13)

The apparatus as described in claim 13 further including requesting the “n” distinct certificates from the distinct certificate authorities.

### Claim 18 (depends on 13)

The apparatus as described in claim 13 wherein “n” is greater than 2.

### Claim 19

A method to authenticate a server to a client, the server having an associated public key, comprising:
specifying a client public key acceptance policy, the client public key acceptance policy identifying a required number of certificates for the server public key that must be received from the server, and a trust function that is applied over information in the certificates and that must be satisfied to establish a client threshold level of trust;
responsive to the client initiating a request for a secure channel to the server, receiving from the server “n” distinct certificates, each of the “n” distinct certificates having been issued to the server by a distinct certificate authority (CA);
determining whether the “n” distinct certificates are valid; and
responsive to a determination that the “n” distinct certificates are valid and are non-overlapping with different root certificate authorities, determining whether certificate chains specified by the received certificates satisfy the trust function of the client public key acceptance policy;
responsive to a determination that the certificate chains specified by the received certificates satisfy the trust function client public key acceptance policy, establishing the secure channel.

### Claim 20 (depends on 19)

The method as described in claim 19 wherein the trust function applies a trust metric over certificate chains in the received certificates.
