SSL Server Selective Certificate Request Logic

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current computer system administration methods often result in user irritation and confusion due to the unnecessary prompting for certificates during SSL session initiation, especially when certificate-based authentication is not required, leading to potential downtime and increased support costs.

Innovation Solution

An SSL server is configured to selectively request certificates based on the authentication method used by the client, differentiating between certificate-based and non-certificate-based authentication by utilizing designated ports or IP addresses, thereby avoiding unnecessary certificate prompts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the SSL server requests certificates from all clients during SSL session initiation, then certificate-based authentication security is improved, but user experience deteriorates due to unnecessary certificate prompts

Engineering Contradiction:
Improvecertificate-based authentication securityVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies local quality by differentiating the authentication process based on client type. The server identifies whether the client is a console system or administrative system and applies certificate prompting only to administrative systems while allowing console systems to bypass certificate prompts. This selective approach maintains security for administrative access while improving user experience for console systems.

Inventive Principle:
Principle #3Local quality

2Reliability

If the SSL server always prompts for certificates, then security verification is improved, but session establishment time increases due to unnecessary authentication steps

Engineering Contradiction:
Improvesecurity verificationVSAvoidsession establishment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by having the server determine the client type and authentication requirements before initiating the certificate prompting process. By identifying console systems in advance and marking them for bypass, the server avoids unnecessary certificate verification steps for these systems, thereby reducing session establishment time while maintaining appropriate security verification for administrative systems.

Inventive Principle:
Principle #10Preliminary action

3Reliability

If certificate-based authentication is required for all SSL sessions, then authentication security is improved, but system complexity increases due to additional authentication configuration

Engineering Contradiction:
Improveauthentication securityVSAvoidauthentication configuration
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the client base into distinct categories: console systems and administrative systems. Each category is assigned different authentication requirements. The server uses designated ports and IP addresses to differentiate between these segments, allowing simplified authentication for console systems while maintaining certificate-based authentication for administrative systems, thereby reducing overall system complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8185945B1Systems and methods for selectively requesting certificates during initiation of secure communication sessions
Publication Date: 2012.05.22 IVANTI INC
  • US8185945B1 patent drawing
  • US8185945B1 patent drawing
  • US8185945B1 patent drawing

AI summary

An exemplary method involves an SSL server receiving an SSL session request from an SSL client. It is determined whether the SSL client is going to use certificate-based authentication. This may involve identifying a port at which the SSL session request was received. Alternatively, this may involve identifying an IP address at which the SSL session request was received. Alternatively still, this may involve examining authentication information in the SSL session request. If the SSL client is going to use certificate-based authentication, a certificate is requested from the SSL client. If the SSL client is not going to use certificate-based authentication, the certificate is not requested from the SSL client.