#1289 TPS UI: Transition TEMP_LOST to TEMP_LOST_TOKEN_FOUND does not exist
Closed: Fixed None Opened 9 years ago by mharmsen.

TPS UI: Transition TEMP_LOST to TEMP_LOST_TOKEN_FOUND does not exist

How reproducible:

always

Steps to Reproduce:

1. TPS CS.cfg has default configuration
2. Enroll an uninitialized or formatted token
3. From TPS UI change the status of the token from Active to Temporarily lost

Actual results:

There is no option to change the status of the temp lost token to token found.
Also temp_lost to active from the UI changes the certs on the token from onHold
to valid.

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

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

Fixed in master:

  • ce872456a09f5c5d146c6cb465b2466ad3ddc73d
  • 9bd94a0a54793a0720b803846ce2291e5064c2ae

Note that the token state FOUND has been renamed to ACTIVE. The "token found" transition represents a status change from TEMP_LOST to ACTIVE.

Metadata Update from @mharmsen:
- Issue assigned to edewata
- Issue set to the milestone: 10.3.0

7 years ago

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

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.

Login to comment on this ticket.

Metadata