Central Certificate Management for Trust Anchor Reduction

Solution Overview

Problem

Current certificate management systems are error-prone and complex, especially for large companies with many message clients, as they require clients to perform chain construction and validation, which can fail due to missing certificates and Authority Information Access (AIA) information, leading to administrative burdens and security risks.

Innovation Solution

A central certificate management system generates and transmits a second certificate with the same public key and issuer field as the original, but signed by another certificate, allowing multiple subjects to use a single trust anchor, reducing the number of trust anchors that need to be downloaded, stored, and validated at clients.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If a central certificate management system is implemented to manage certificates for multiple subjects, then the administrative burden and control are improved, but the complexity of certificate chain construction and validation increases for clients

Engineering Contradiction:
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The central certificate management system pre-constructs certificate chains and determines validity before clients need them. The system performs chain construction and validation in advance, storing the results so clients can directly use pre-validated certificates without performing complex chain construction themselves.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The central certificate management system acts as an intermediary between the certificate authority and clients. It receives certificates from the authority, performs chain construction and validation, and delivers pre-validated certificates to clients, shielding them from the complexity of the validation process.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If clients perform chain construction and validation themselves, then autonomy is improved, but errors increase due to missing certificates and AIA information

Engineering Contradiction:
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system maintains client autonomy by allowing them to request and receive certificates independently. However, the central management system performs the complex chain construction and validation tasks that clients would otherwise have to perform themselves, eliminating errors related to missing certificates and AIA information while preserving operational independence.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If multiple trust anchors are distributed to clients for different subjects, then certificate versatility is improved, but the number of trust anchors to be downloaded, stored, and validated increases

Engineering Contradiction:
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The central certificate management system merges multiple trust anchors into a single centralized repository. Instead of distributing multiple trust anchors to each client, the system consolidates them centrally and performs validation against this unified set, reducing the number of trust anchors clients must download and store while maintaining the ability to validate certificates from multiple issuers.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3076583B1Central certificate management
Publication Date: 2019.10.09
  • EP3076583B1 patent drawingFigure 1~2
  • EP3076583B1 patent drawingFigure 3~4
  • EP3076583B1 patent drawingFigure 5~6

AI summary

Certificate management for a plurality of clients: receiving a first certificate (41) for a subject comprising a public key, an issuer field with an issuer and a serial number field with a serial number, wherein the first certificate (41) for the subject is signed by a first certificate for the issuer; generating a second certificate (42) for the subject comprising the public key, an issuer field with the issuer and a serial number field with the serial number, wherein the second certificate (42) for the subject is signed by a second certificate (43) for the issuer being different to the first certificate for the issuer; and transmitting the second certificate (42) for the subject to one of the plurality of clients; and performing an action on the basis of the public key of the second certificate (42) for the subject.