Installation guide

Table 5. Fixed Bugs
Bug Number Description
209213 There was a random error in the Enterprise Security Client that
when an enrolled card was inserted and removed, the Reset
Password window would not allow users to type in a new password.
211053 There Enterprise Security Client would not restart on Microsoft
Windows Vista after the machine was rebooted, so the client would
have to be started manually.
223309 When a CA was cloned, certain attributes that are required for the
clone were not properly copied over, including attributes containing
the CA certificates. This meant that the cloned CA could not function.
223367
224902
When a subsystem configuration failed or if a subsystem were
uninstalled and then a new instance, with the same instance name
was created, then the configuration would fail at the internal
database configuration window because there was no way to
overwrite the existing database with the same name. A new
checkbox has been added that allows the new instance to reuse the
database name.
224691 With two T PS instances on the same server, if one instance were
restarted, then the other one would be stopped.
224765 When cloning a CA, the configuration wizard would claim that a new
administrator certificate was generated and imported into the
browser, even though no certificate was created.
224889 If a TPS was configured not to support server-side key generation,
the DRM-related server-side key generation parameters were still
added to the CS.cfg file with wrong values.
240083
241423
Inconsistently, expired certificates were included and published in
new CRLs.
243921
490461
Publishing certificates and CRLs to a text file (file-based publishing)
failed.
245661 Cloning a DRM on an HSM resulted in numerous errors, such as
Java null pointer exceptions, authorization failures, and improper
configuration for the instance state, request numbers, and serial
numbers.
246252 A CA would accept a certificate request which was signed with an
obviously bad signature because it only verified the certificate
request itself.
250188 During subsystem configuration, the Authority Key Identifier
extension was not be generated on the issued subsystem
certificates.
251226 Opening the CA console threw a null pointer exception referencing
the CMSAdmin class because of a misnamed jar file.
251569
The search time limit for end-entities pages set in the web.xm l file
was being inconsistently ignored, which could allow the LDAP
6. Bugs Fixed in Certificate System 8.0
13