Este contenido no está disponible en el idioma seleccionado.
7.4. Post-installation Tasks
Once installation using the
pkispawn utility is complete, certain actions are required after the installation. In addition, some optional actions would also be helpful, depending on the site's preferences.
For optional procedures, see Part III, “Configuring Certificate System”. Useful post-installation-step procedures include:
- Configuring or adding certificate enrollment profiles (CA). For details, see Section 11.1, “Creating and Editing Certificate Profiles Directly on the File System”
For required procedures, perform the actions described below in Section 7.4, “Post-installation Tasks” after you have installed Certificate System.
7.4.1. Setting Date/Time for RHCS Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
It is important that the time is correct for running RHCS; see Chapter 15. Setting Time and Date in Red Hat Enterprise Linux 7.6 in Red Hat Certificate System's Administration Guide.
7.4.2. Replacing a Temporary Self-Signed Certificate in Directory Server (CA) Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
When the internal LDAP server was created initially with a temporary self-signed server certificate, this is time to replace it with a new certificate that is issued by the CA you just installed.
For details, see Section 6.5.4, “Replacing the Temporary Certificate”.
7.4.3. Enabling TLS Client Authentication for the Internal LDAP Server Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Red Hat Certificate System is required to communicate with its internal LDAP server via TLS mutual authentication. For further details see Enabling TLS Client Authentication.
7.4.4. Configuring Session Timeout Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Various timeout configurations exist on the system that could affect how long a TLS session is allowed to remain idle before termination. For details, see Section 9.4.1.3, “Session Timeout”.
7.4.5. CRL or Certificate Publishing Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
CRL publishing is critical in providing OCSP service. Certificate publishing is optional but often desired by sites. For details, see Chapter 7. Publishing Certificates and CRLs in Red Hat Certificate System Administration Guide.
7.4.6. Disabling Certificate Enrollment Profiles (CA) Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Only CMC certificate enrollment profiles are allowed. All other profiles need to be disabled.
For details, see Section 11.1.5, “Disabling Certificate Enrolment Profiles”.
7.4.7. Enabling Access Banner Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
User interface banners are required.
For details, see Section 9.5.1, “Enabling an Access Banner”.
7.4.8. Enabling the Watchdog Service Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
The watchdog (
nuxwdog) service provides secure system password management.
For details, see Section 9.3.2.1, “Enabling the Watchdog Service”.
7.4.9. Configuration for CMC Enrollment and Revocation (CA) Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Certificate enrollments and revocation have to be done via CMC.
- For details about enabling the CMC Shared Token Feature, see Section 9.6.3, “Enabling the CMC Shared Secret Feature”.
- For details about enabling the
PopLinkWittnessfeature, see Section 9.6.2, “Enabling thePopLinkWittnessV2Feature”. - For details about enabling
CMCRevokefor the web user interface, see Section 9.6.4, “Enabling CMCRevoke for the Web User Interface”.
7.4.10. Requiring TLS client-authentication for the Java Console Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Certificate System administrators are required to present a user TLS client certificate when logging into the Java console. See Section 9.2.3.14, “Setting Requirement for
pkiconsole to use TLS Client Certificate Authentication”.
7.4.11. Creating a Role User Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Real role users have to be created so the bootstrap user could be removed.
Create users and assign them to different privileged roles to manage Certificate System. See Chapter 14, Creating a Role User.
7.4.12. Removing the Bootstrap User Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Bootstrap user is to be removed once the real role users are created.
After creating a new administrator account which is assigned to an individual person, remove the account which was automatically created during the installation. For details, see Chapter 15, Deleting the Bootstrap User.
7.4.13. Disabling Multi-role Support Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Once the bootstrap user is removed, the multi-role support needs to be disabled.
For details, see Section 15.1, “Disabling Multi-roles Support”.
7.4.14. KRA Configurations Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
7.4.14.1. Adding Requirement for Multiple Agent Approval for Key Recovery Authority (KRA) Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Multiple KRA agents are required to approve key recovery.
7.4.14.2. Configuring KRA Encryption Settings Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Only certain key encryption/wrapping algorithms are allowed. For details, see Section 12.2, “Encryption Of KRA Operations”.
7.4.15. Setting up Users to use User Interfaces Copiar enlaceEnlace copiado en el portapapeles!
Copiar enlaceEnlace copiado en el portapapeles!
Before a user could use an approved user interface, initialization needs to be performed.
Users (administrative roles or otherwise) are required to setup their clients for accessing the user interface. See 2.1. Client NSS Database Initialization in Red Hat Certificate System's Administration Guide.