dogtagpki

#1288 TPS transition 6:4, terminated token is successfully enrolled with a different user using tpsclient
Closed: Duplicate Opened by mharmsen.

Closed: Duplicate
Reopen Issue

TPS transition 6:4, terminated token is successfully enrolled with a different
user using tpsclient

How reproducible:

always

Steps to Reproduce:

1. Edit tps CS.cfg to have tps.operations.allowedTransitions=0:0,0:4,4:0,6:4
2. Restart the server
3. Enroll an uninitialized/formatted token using tpsclient
4. From TPS UI change the status of the token from Active to terminated
5. Enroll the terminated token for a different user using tpsclient.

Actual results:

Enrollment is successful.

Expected results:

Enrollment should fail.

Per CS/DS meeting of 03/02/2015: 10.2.3

Moving to 10.2.4 per CS team meeting.

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

Adding new transitions into tps.operations.allowedTransitions is disallowed. The default transition list has been updated in ticket #1290.

Metadata Update from @mharmsen:
- Issue assigned to jmagne
- Issue set to the milestone: 10.3.1

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

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
None
None
None
Normal
defect
TPS
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.