TPS UI: Token change status operation, transition from Uninitialized to Active is successful but no certificate found for the token under certificates
How reproducible:
always
Steps to Reproduce:
1. Format an Uninitialized token 2. From the UI, select the token in Uninitialized state 3. Change the status from Uninitialized to Active
Actual results:
This change is successful but cannot find any certificates for the token under the Certificates tab of the UI
Expected results:
Change status from Uninitialized to Active should not be allowed. Uninitialized to Active should happen only after enrollment of the token.
Per 10.2.3 Triage meeting of 02/26/2015: 10.2.3
OK, I know what is going on here.
There are two types of states, UI states and operations states.
tokendb.allowedTransitions=0:1,0:2,0:3,0:4,0:5,0:6,3:4,3:5,3:6,4:1,4:2,4:3,4:6
The preceding allowedTransitions (UI transtions) has the one 0:4 which is "unitialized" to "FOUND".
This should probably not be in the list. Also the UI calls this transition "ACTIVE". ACTIVE is really an operation transition that has the same number as FOUND, which is set with the UI.
Two things to fix this. Take out the 0:4 transition from the UI transistion list. Also change the name of the state to "FOUND" in the UI.
When a formatted token is enrolled with the server its state goes from 0 "unitialized" to 4 "active".
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
This requires:
Fixed in master:
Metadata Update from @mharmsen: - Issue assigned to edewata - Issue set to the milestone: 10.3.0
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/1837
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.