# US 2026/0039484 A1 · Secure certificate chain transition

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

- Number: US 2026/0039484 A1
- Document ID: US20260039484A1
- Status: Published application
- Kind: A1
- Application number: 19/355,312
- Filed: 2025-10-10
- Published: 2026-02-05
- Earliest claimed: 2024-02-27
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Karim SALEM; Avanindra PARUCHURI; Alexander Geoffrey HOWELLS; George Adrian DRUMEA; Zhifeng WANG
- Web page: https://patentgrep.com/patent/US20260039484A1

## CPC

- H04L 9/3265: {using certificate chains, trees or paths; Hierarchical trust model}
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- G06F 21/33: using certificates
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- H04L 9/3268: {using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]}
- 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

Some embodiments provide proxies or other servers in a computing network with independent certificate chains which facilitate mitigation of certificate problems. Independence criteria are enforced against two or more installed certificate chains on a given server, identifying and avoiding dependencies such as cross-certification, shared certificate authorities, shared revocation lists, or shared certificate status protocol endpoints between the certificate chains. Some embodiments serve independent certificates concurrently in an active-active certificate server configuration. The certificate chains' coexistence and their independence from one another facilitates transitioning the network from a failing issuer or a failed chain to a chain that works better, thereby improving network resilience and limiting damage from certificate problems. By dynamically updating certificate bindings, some embodiments also facilitate safe deployment of new certificates during migration from one issuer to another. Certificate distributions are computed from issuer ratios, network topology, or both.

## Claims

### Claim 1

A computing system configured to manage certificate bindings in a computing network, the computing system comprising:
at least one hardware processor; and
at least one memory device operably coupled to the at least one hardware processor and storing instructions that, when executed by the at least one hardware processor, cause the computing system to:
maintain a plurality of certificate chains, wherein a first certificate chain comprises a digital certificate issued by a first certificate authority and is bound to a first identity in the computing network, and a second certificate chain comprises a digital certificate issued by a second certificate authority and is bound to the first identity, and wherein the first certificate chain and the second certificate chain are issued by different certificate authorities;
detect a certificate validation issue associated with the first certificate chain;
automatically update a certificate binding for the first identity to utilize the digital certificate from the second certificate chain; and
perform the update without requiring a restart of a web server or a reload of an application process configured to serve the first identity.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein the certificate validation issue comprises one or more of:
expiration of a certificate in the first certificate chain;
revocation of a certificate in the first certificate chain;
a failure to access a certificate authority associated with the first certificate chain; or
a failure to validate the first certificate chain through an online certificate status protocol or certificate revocation list mechanism.

### Claim 3 (depends on 1)

The computing system of claim 1, wherein the instructions further cause the computing system to:
verify that the first certificate chain and the second certificate chain are independent prior to performing the update.

### Claim 4 (depends on 3)

The computing system of claim 3, wherein the instructions to verify that the first certificate chain and the second certificate chain are independent prior to performing the update further cause the at least one hardware processor to:
confirm that the first certificate chain and the second certificate chain do not share at least one of:
a root certificate;
an intermediate certificate;
a certificate revocation list;
a certificate revocation list distribution point; or
an online certificate status protocol endpoint.

### Claim 5 (depends on 1)

The computing system of claim 1, wherein the instructions further cause the at least one processor to:
select the second certificate chain according to a certificate selection policy comprising at least one of:
a predetermined percentage allocation;
a topology of the computing network;
a random or quasi-random distribution; or
a current health metric associated with one or more certificate authorities.

### Claim 6 (depends on 1)

The computing system of claim 1, wherein the instructions further cause the at least one processor to:
incrementally alter the percentage of certificate bindings allocated to the first certificate chain and the second certificate chain over time based on observed validation performance.

### Claim 7 (depends on 1)

The computing system of claim 1, wherein the instructions to perform the update without requiring a restart of the web server or a reload of the application process configured to serve the first identity further cause the at least one processor to:
reconfigure a TLS binding of the web server at runtime through an application programming interface.

### Claim 8

A method for managing certificate bindings in a computing network comprising:
maintaining at least two certificate chains comprising a first certificate chain and a second certificate chain, wherein:
the first certificate chain comprises a digital certificate issued by a first certificate authority and is bound to a first identity in the computing network;
the second certificate chain comprises a digital certificate issued by a second certificate authority and is also bound to the first identity; and
the first certificate authority and the second certificate authority are different certificate authorities;
detecting a certificate validation issue associated with the first certificate chain; and
automatically updating a certificate binding for the first identity to utilize the digital certificate from the second certificate chain responsive to detecting the certificate validation issue, wherein the update is performed without requiring a restart of a web server or a reload of an application process configured to serve the first identity.

### Claim 9 (depends on 8)

The method of claim 8, wherein detecting the certificate validation issues associated with the first certificate chain comprises:
detecting the certificate validation issue based on telemetry data collected from client connection attempts or handshake failures associated with the first certificate chain.

### Claim 10 (depends on 8)

The method of claim 8, wherein the method further comprises:
selecting the second certificate chain for the update according to a certificate selection policy comprising at least one of:
a predetermined percentage allocation;
a topology of the computing network;
a random or quasi-random distribution; or
a current health metric associated with one or more certificate authorities.

### Claim 11 (depends on 8)

The method of claim 8, wherein the method further comprises:
proactively initiating the update to utilize the digital certificate from the second certificate chain prior to expiration of a certificate in the first certificate chain.

### Claim 12 (depends on 8)

The method of claim 8, wherein the at least two certificate chains are maintained on distinct certificate servers operating in an active-active configuration, such that different certificates for the first identity are concurrently served by different servers within a defined time period.

### Claim 13 (depends on 8)

The method of claim 8, wherein the first identity comprises at least one of:
a domain name;
a server name indication;
an IP address; a port identifier; or
a client identity.

### Claim 14 (depends on 8)

The method of claim 8, wherein the method further comprises:
verifying that the first certificate chain and the second certificate chain are independent prior to performing the update by confirming that the first certificate chain and the second certificate chain do not share at least one of:
a root certificate;
an intermediate certificate;
a certificate revocation list;
a certificate revocation list distribution point; or
an online certificate status protocol endpoint.

### Claim 15

A non-transitory computer-readable medium storing instructions that, when executed by one or more processors of a computing system, cause the computing system to:
maintain in memory a first certificate chain and a second certificate chain, wherein the first certificate chain and the second certificate chain are bound to a first identity in a computing network and issued by different certificate authorities;
monitor certificate validation status for the first certificate chain during runtime;
detect a certificate validation issue associated with the first certificate chain based on the certificate validation status;
select the second certificate chain as a replacement in accordance with a certificate chain selection policy; and
bind the second certificate chain to the first identity without restarting a web server or reloading an application process associated with the first identity.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the instructions to detect the certificate validation issue based on the certificate validation status further cause the computing system to:
analyze telemetry data associated with client connection attempts or handshake failures involving the first certificate chain.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the certificate chain selection policy comprises at least one of:
a certificate authority health metric;
a topology of the computing network;
a predetermined percentage allocation; or
a randomized distribution.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the instructions further cause the computing system to:
verify that the first certificate chain and the second certificate chain are independent by confirming that they do not share any of:
a root certificate;
an intermediate certificate;
a certificate revocation list; a certificate revocation list distribution point; or
an online certificate status protocol endpoint.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the instructions to bind the second certificate chain to the first identity without restarting the web server or reloading the application process further cause the computing system to:
reconfigure a transport layer security binding via a runtime application programming interface.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the certificate validation issue comprises one or more of:
expiration of a certificate in the first certificate chain;
revocation of a certificate in the first certificate chain;
a failure to access a certificate authority associated with the first certificate chain; or
a failure to validate the first certificate chain through an online certificate status protocol or certificate revocation list mechanism.
