dogtagpki

#1317 Key change over rollback operation fails using tpsclient tool
Closed: migrated by dmoluguw. Opened by mharmsen.

Closed: migrated
Reopen Issue

Key change over rollback operation fails using tpsclient tool

How reproducible:

always

Steps to Reproduce:

1. Create a master key on TKS instance
2. add the following params to TKS CS.cfg
tks.mk_mappings.#02#01=token_name:nickname
tks.defKeySet.mk_mappings.#02#01=token_name:nickname
3. Add the following params to TPS CS.cfg
op.enroll.userKey.update.symmetricKeys.enable=true
op.enroll.userKey.update.symmetricKeys.requiredVersion=2
4. enroll a token using tpsclient tool. Enrollment will be successful and TPS
UI will show the key as 0201 for the token
5. Change the key param in TPS CS. cfg to
op.enroll.userKey.update.symmetricKeys.requiredVersion=1
6. Attempt an enrollment operation

Actual results:

Enrollment fails

Expected results:

Enrollment should be successful

Additional info:

The same operation work successfully using smartcard token

Per CS/DS Meeting of 03/30/2015: 10.3

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

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/1879

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)
Metadata
None
None
None
None
Normal
defect
General
QE
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.