#2359 LWCA initialisation fails in cert update
Closed: Fixed None Opened 7 years ago by ftweedal.

If an LWCA entry is read with the authoritySerial attribute,
and the serial differs from the known serial or the serial
was previously unknown, Dogtag attempts to update the certificate.
The procedure is carried out during initialisation, and if it fails
and exception is thrown, preventing the CA from being added.

If the key is not yet in the NSSDB, the update is certain to
fail. This can happen e.g. if CA is created on one clone while another
clone is down. When the other clone comes up, it will immediately
see the authoritySerial and fail to initialise it.


Pushed to master (41aef5254c20301851716ef46b614d185b33a87b)

Metadata Update from @ftweedal:
- Issue assigned to ftweedal
- Issue set to the milestone: 10.3.3

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2479

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.

Metadata