This section describes how to install, configure, and use InfoConnect to operate within the Department of Defense (DOD) or other Public Key Infrastructure (PKI) environment. PKI configuration affects both Secure Shell and SSL/TLS connections.
Running Reflection in DOD PKI mode
By default, Reflection applications allow some configurations that do not meet DOD PKI requirements. Administrators can use Reflection Group Policies to configure all Reflection sessions to meet DOD PKI requirements.
To configure DOD PKI mode
Run the Group Policy Editor using one of the following techniques:
On the command line, enter Gpedit.msc
In the Active Directory Users and Computers console, open the properties for an Organizational Unit, click thetab, and edit or create a new policy object.
Install the Reflection template (ReflectionPolicy.adm) if you have not already done so.
NOTE:For information about how to download and install the Reflection policy template, see https://download.attachmate.com/fileinfo.asp?filename=ReflectionPolicy.zip
Under> > > , disable the setting .
Configuring DOD PKI mode has the following effects.
You must configure InfoConnect to use either CRL A digitally signed list of certificates that have been revoked by the Certification Authority. Certificates identified in a CRL are no longer valid. checking or an OCSP A protocol (using the HTTP transport) that can be used as an alternative to CRL checking to confirm whether a certificate is valid. An OCSP responder responds to certificate status requests with one of three digitally signed responses: "good", "revoked", and "unknown". Using OCSP removes the need for servers and/or clients to retrieve and sort through large CRLs. responder. In DOD PKI mode, the option to use neither form of checking is disabled. (For SSH connections, certificate revocation is configured using the PKI tab of the Secure Shell settings dialog box. For SSL/TLS connections it is configured using the PKI Configuration dialog box.)
InfoConnect enforces FIPS-approved encryption algorithms. For SSH connections, this means that only FIPS-approved options are available on the Encryption tab of the Secure Shell settings dialog box. For SSL/TLS connections this means that you cannot setto 40 Bits or 56 Bits.
For a connection to succeed, the certificate host name must exactly match the host name specified for your connection. This means that the setting tab of the dialog box. For SSL/TLS connections it is configured using the dialog box.)is automatically selected and cannot be modified. (For SSH connections, this setting is configured using the
Intermediate CA certificates signed using the MD2 or MD5 hash are not supported for certificate validation.
Installing and Removing Trust Points
A trust point is any CA certificate in a chain of trust.
To add a trust point to the Reflection certificate store:
Click, then browse to locate a certificate (typically *.cer or *.crt).
To remove a trust point from the Reflection Certificate Manager store,
Select the certificate and click.
Intermediate CA trust points can be retrieved from an LDAP or HTTP server which may be identified by explicit URIs defined in the Authority Information Access (AIA) extension of a certificate, or using LDAP server information configured on the LDAP tab of the Reflection Certificate Manager. These certificates are stored in the cert_cache file located in either <My Documents>\Micro Focus\Infoconnect\.pki or %programdata%\Micro Focus\Reflection\.pki.
When Reflection is running in DOD PKI mode, only those root certificates you have added to the Reflection Certificate manager are used. There is no need to remove any non-DOD PKI certificates that may be present in the Windows Certificate Store.
Configuring Certificate Revocation Checking
InfoConnect's default value for certificate revocation checking is based on your current system setting. If your system is configured to do CRL checking, InfoConnect sessions will check for certificate revocation using CRLs A digitally signed list of certificates that have been revoked by the Certification Authority. Certificates identified in a CRL are no longer valid. by default. You can also configure InfoConnect to use an OCSP A protocol (using the HTTP transport) that can be used as an alternative to CRL checking to confirm whether a certificate is valid. An OCSP responder responds to certificate status requests with one of three digitally signed responses: "good", "revoked", and "unknown". Using OCSP removes the need for servers and/or clients to retrieve and sort through large CRLs. responder.
InfoConnect also supports a setting to disable CRL checking. You may want to use this setting for testing purposes, however this option is not available if InfoConnect is running in DOD PKI mode.
CAUTION:Disabling CRL checking compromises your security. Use this option only for testing purposes.
You can define one or more LDAP servers from which to retrieve intermediate certificates or CRLs.
To define an LDAP server
Click, then specify the server using the following URL format:
To configure OCSP
You can define one or more OCSP servers from which to request certificate revocation information.
Setto . (For SSH connections use the PKI tab of the Secure Shell settings dialog box. For SSL/TLS connections use the PKI Configuration dialog box.)
NOTE:OCSP responder URLs required by a certificate are identified in the AIA extension of the certificate. If this information is not provided in the certificate, you can use the following steps to configure OCSP responder information.
Click, then specify the server using the following URL format:
Using Uniform Resource Identifiers for DOD PKI Services
InfoConnect supports the use of URIs for automatic CRL A digitally signed list of certificates that have been revoked by the Certification Authority. Certificates identified in a CRL are no longer valid. updating and retrieval. As defined in section 22.214.171.124 of RFC3280.
If CRL checking is enabled, InfoConnect checks for certificate revocation as follows:
Check the crl_cache file for valid revocation information. If none is found, continue on to step 2.
Check the CDP extension in the certificate for HTTP or LDAP URIs and query these in the order specified (first HTTP, then LDAP). If the certificate is found to be revoked, close the connection. If the certificate is not found continue on to step 3.
If one or more LDAP servers is specified in the Reflection Certificate Manager LDAP tab, assemble the Distinguished Name for the CA listed in the Issuer extension of the certificate and query for the CRL file. If the certificate is not found to be revoked in any CRL, continue to the next validation step.
Updates for expired CRLs are handled automatically, and do not require administrator intervention or configuration.
If OCSP checking is enabled, InfoConnect always checks all available OCSP responders to ensure that the connection will fail if any of these responders knows that the certificate has been revoked. For the connection to succeed at least one OCSP responder must be available and return a value of 'good' for the certificate status. InfoConnect performs these checks as follows.
Check the AIA extension in the certificate for one or more OCSP responders and query each of those responders. If the status of the certificate comes back as 'revoked' from any responder, close the connection.
Check for one or more user configured OCSP responders specified using the Reflection Certificate Manager OCSP tab and query each of those responders. If the status of the certificate comes back as 'revoked' from any responder, close the connection.
If all responders returned 'unknown' close the connection. If a 'good' response was returned from at least one of the queried OCSP responders continue on to the next validation step.
Using URIs to Retrieve Intermediate Certificates
As defined in section 126.96.36.199 of RFC3280, InfoConnect can use URIs to retrieve intermediate CA certificates as follows:
Check the cert_cache file for the required intermediate certificate. If it is not found, continue on to step 2.
If either HTTP or LDAP URIs are defined in the Authority Information Access (AIA) extension of a certificate, attempt to use these (first HTTP, then LDAP) to retrieve intermediate CA certificates.
If the preceding attempts fail, assemble a Distinguished Name from the issuing certificate's Subject Name, and queries the defined LDAP server for the contents of the CACertificate attribute.
Because InfoConnect does not enforce the security policy extension of a certificate, security policy configuration is not necessary.
Configuring and Protecting Certificates and Private Keys
To configure client authentication using certificates:
On thetab, click , then browse to locate a certificate (typically *.pfx or *.p12). You will be prompted to create a passphrase that will be required any time this key is used. Entering a passphrase is advisable to help protect this key on your system.
For Secure Shell connections, open thedialog box, click the tab and select the certificate(s) you want to use for client authentication to the currently specified host. (This step is not required for SSL/TLS connections.)
Private Key Safeguards
If a client private key is stolen, a malicious user can gain access to files on any servers accessible to that user. To minimize this risk, each client user should always protect his or her private key with a passphrase. This ensures that only someone who knows the passphrase can authenticate with that key. Users should create and protect passphrases following the password specifications in your organization’s Security Policy.
Actions to Take if a Key is Compromised
Consider a private key compromised if it has become available to any unauthorized entity, or if you have reason to distrust the actions of any person who has access to the key.
If the client key is compromised, revoke the client certificate.
To replace a compromised key:
Generate a new private key and certificate and import the key into the Reflection Certificate Manager.
On the server, update the map file line for this client if the identifying information has changed.
To remove the compromised key from the client computer: