#3073 verify_certificate_exists still fails when token is empty
Closed: fixed 5 years ago Opened 5 years ago by cheimes.

Commit https://github.com/dogtagpki/pki/commit/17677ae4d2cda456b64ec67e2b25ba63f4a58a70 changed how default token name is handled. Dogtag now passes None to signal default internal token. However verify_certificate_exists method was not changed. This bug breaks some of FreeIPA CI tests like TestServerReplicaCALessToCAFull.


Metadata Update from @cheimes:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None

5 years ago

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Metadata Update from @edewata:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1643101
- Issue assigned to cheimes
- Issue set to the milestone: 10.6.8

5 years ago

Metadata Update from @edewata:
- Issue status updated to: Open (was: Closed)

5 years ago

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

5 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/3190

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