#3073 verify_certificate_exists still fails when token is empty
Closed: fixed Opened 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.


PR https://github.com/dogtagpki/pki/pull/80

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

Committed https://github.com/dogtagpki/pki/commit/0fba3c2710ee14f2d4ddb2bd401ed6d592f3f2b8

The fix has been pushed to master:
* https://github.com/dogtagpki/pki/commit/0fba3c2710ee14f2d4ddb2bd401ed6d592f3f2b8

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

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

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

Apparently there is a related bug:
https://github.com/dogtagpki/pki/pull/83

Fixed in master branch:
* https://github.com/dogtagpki/pki/commit/54edd1a7dd4e7e49bff4ef4fde15fc4d97802b00

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

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.

Metadata