I just tried this out on my own system, which consists of the freshly checked in scp02 work, but it should not be a factor. I did this:

1. Enrolled a token with tpsclient.
2. Went into the UI and set the status to temp lost.
3. Went back to tpsclient and retried the enrollment.
4. It failed with the following message:

TPSSession.process: Message processing failed: Operation for CUID 40906145C76224192D2B Disabled, illegal transition attempted TEMP_LOST to ACTIVE

Per CS/DS Meeting of 03/09/2015: 10.2.3

Per Dogtag 10.2.x TRIAGE meeting of 04/28/2015: (Tech Preview Feature)

Per CS/DS meeting of 06/08/2015: 10.2.6

Per Dogtag 10.2.6 TRIAGE meeting of 06/30/2015: 10.3

The 3:4 transition was removed from the default tokendb.allowedTransitions in ticket #1808. However, if the user adds the transition manually into tokendb.allowedTransitions, the UI might allow that transition to happen. Since this is an illegal transition, the TPS probably should specifically reject the 3:4 transition if it's added to tokendb.allowedTransitions.

The default list should be updated to include all supported transitions. Unwanted transitions can be removed from the list, but new transitions cannot be added to the list if they are not part of the default supported transitions.

The list should be validated in TPS selftest, so if the list contains illegal/unsupported transitions the TPS should not start.

Fixed in master:

• 00e4765342c56c0a010e3de6929f1a5b2585ed03

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

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.