dogtagpki

#2307 Token State doesn't get change from Active to Temporary lost.
Closed: migrated by dmoluguw. Opened by myusuf@redhat.com.

Closed: migrated
Reopen Issue

When we modify values for tokendb.allowedTransitions in CS.cfg file of TPS,
token status is not changing from Active state to Temporary lost. It throws the
following error in modal window when tried to change the state form active to
temporary lost.

 "Can't find resource for bundle java.util.PropertyResourceBundle, key
TEMP_LOST.TEMP_LOST_PERM_LOST"

Steps to Reproduce:

1. Edit the CS.cfg file:
  - Replace the values of tps.operations.allowedTransitions as
tps.operations.allowedTransitions=0:0,0:4,4:6,6:0,4:0
  - Replace the values of tokendb.allowedTransitions as:
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
2. Restart the subsystem.
3. Go to the TPS UI -> click "Tokens" from Navbar or from Token Management
pane.
4. Select a Token -> click on "Change Status" form top left of the screen.
5. Select "This token has been temporarily lost", click on Save button.

Actual results:

 HTTP Error 500:
Can't find resource for bundle java.util.PropertyResourceBundle, key
TEMP_LOST.TEMP_LOST_PERM_LOST

Expected results:

Token status should be change to the temporary lost.

Additional info:

When restored the CS.cfg file contents to its default, TPS UI shows the status
of token as Temporarily lost.
Attachment 1148876 in associated bug:  tps debug logs

Per Bug Triage of 05/03/2016: 10.4

Metadata Update from @myusuf@redhat.com:
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue set to the milestone: 10.4 (was: UNTRIAGED)

Per CS/DS Meeting of August 7, 2017, it was determined to move this issue from 10.4 ==> FUTURE.

Metadata Update from @mharmsen:
- Issue set to the milestone: FUTURE (was: 10.4)

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

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 Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)
Metadata
None
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.