Creating the CA Certificate Symlinks - Analytics Database - Teradata Vantage

Teradata Vantage™ - Analytics Database Security Administration - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-05-03
dita:mapPath
hjo1628096075471.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
zuy1472246340572
Product Category
Teradata Vantage

You can create symlinks to help OpenSSL locate certificates faster. If a directory server provides a certificate, OpenSSL hashes the subject and serial number of the certificate, and then opens symlinks having the same hash code until it finds the certificate. The symlinks provide an indexing criteria that eliminates the need for OpenSSL to sift through every available certificate.

The previous Example: Certificate Chain example contains two certificates. You must store each of these certificates in a file before beginning the hashing process that creates the symlinks. OpenSSL cannot use these files directly. Instead, it uses a file with a filename that is the hash code (rendered in readable hexadecimal) and an extension that is a decimal number starting with 0 to be created, in the form:

hashcode.number

This scheme allows certificates that have identical hashes to be represented as separate symlinks.