- Hardware Appliance Unboxing
- Initial Set-up
- Restore from Backup
- Connect to Cluster
- Using External CA for Installation
- Basic Hardware Operations
- WebConf - Configurator of Hardware Appliance
- Certificates and Trusted CAs
- Setting up a Validation Authority (VA)
- HA Setup
- PKCS#11 Slot Smart Card Activation
- EJBCA Administration
- Certificate Life Cycle Management
Creating CA Hierarchy
- Step 1: Create the RootCA
- Step 2: Create Certificate Profile for SubCAs
- Step 3: Create End Entity Profile for SubCAs
- Step 4: Import RootCA as External CA in Node A
- Step 5: Create SignCA as SubCA in Node A
- Step 6: Create AuthCA as SubCA in Node A
- Step 7: Create SSLCA as SubCA in Node A
- Step 8: Create Certificate Profiles for End Entities that use the SubCAs
- Step 9: Create End Entity Profiles for SubCAs
- Step 10: Create End Entities that use the SubCAs
- Managing End Entities
- Creating Java Truststore
- Check for Weak Debian Keys
- Hardware Appliance 3.5.4 Release Notes
- Hardware Appliance 3.5.3 Release Notes
- Hardware Appliance 3.5.2 Release Notes
- Hardware Appliance 3.5.1 Release Notes
- Hardware Appliance 3.5.0 Release Notes
- PKI Appliance 3.4.5 Release Notes
- PKI Appliance 3.4.4 Release Notes
- PKI Appliance 3.4.3 Release Notes
PKI Appliance 3.4.2 Release Notes
PKI Appliance 3.4.1 Release Notes
- Release Notes Summary
- Hardware Appliance 3.5.X Upgrade Notes
PKI Appliance 3.4.5 Release Notes
This maintenance release of PKI Appliance and SignServer Appliance version 3.4.5 delivers EJBCA Enterprise 22.214.171.124.
EJBCA Enterprise 126.96.36.199
The EJBCA Enterprise 188.8.131.52 maintenance release resolves vulnerabilities found in EJBCA during penetration testing.
For more information, refer to the EJBCA Release Notes.
Improvements and Fixes
- Accessing JBoss CLI, required by some advanced customers, has been simplified compared to the access method introduced in version 3.3.0.
- As of Appliance version 3.3.0, we did not deliver a truststore of trusted CAs for outgoing connections with our Java installations. This has been improved as of the 3.4.5 release.
- We have resolved the issue that previously caused a backup to occasionally not restore without manual interaction. This only occurred under certain circumstances such as old generation hardware, legacy PKCS#11 stack and smart card activation for PKCS#11 slots.
For important upgrade information and limitations to be aware of, review the Upgrade Notes.