#2509 Token re-enroll fails when cert overwrite parameters are set to false
Closed: migrated 3 years ago by dmoluguw. Opened 7 years ago by rpattath.

Token re-enroll fails when cert overwrite parameters are set to false

Steps to Reproduce:

1. Set the following params in TPS CS.cfg
op.enroll.userKey.keyGen.encryption.overwrite=false
op.enroll.userKey.keyGen.signing.overwrite=false
2. Enroll a token
3. Re-enroll the token

Actual results:

Re-enroll fails

Expected results:

re-enroll should be successful and the certs on the token should not be
overwritten.

Additional info:

The debug log attached to corresponding Bugzilla Bug.

Per PKI Bug Council of 10/18/2016: 10.4

jmagne to investigate

Metadata Update from @rpattath:
- Issue set to the milestone: UNTRIAGED

7 years ago

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue set to the milestone: 10.4 (was: UNTRIAGED)

7 years ago

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

Metadata Update from @mharmsen:
- Issue set to the milestone: FUTURE (was: 10.4)

6 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/2629

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata