TPS UI: Change state of a token from TEMP_LOST to TEMP_LOST_PERM_LOST not possible from the UI
How reproducible:
always
Steps to Reproduce:
1. TPS CS .cfg has default config 2. Enroll an uninitialized/formatted token 3. Change state of the token to temp lost
Actual results:
No option to change from TEMP_LOST to TEMP_LOST_PERM_LOST from the UI. The only possible option from UI is TEMP_LOST to PERM_LOST which is not allowed.
Expected results:
When the token is in the temp lost state the only change state options available on the UI should be token found, temp lost token perm lost, temp lost token terminated
Additional info:
The following is successful and the token has a PERM_LOST status: curl -E TPS1_agentV:Secret123" -X POST -k https://sigma.lab.eng.rdu.redhat.com: 30042/tps/rest/tokens/10000000000000000089?status=TEMP_LOST_PERM_LOST
Per CS/DS meeting of 03/02/2015: 10.2.3
This will be fixed by ticket #1275.
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
Need to investigate the backend functionality.
Fixed in master:
The TEMP_LOST_PERM_LOST has been replaced with PERM_LOST because they are actually identical.
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/1853
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.