#1684 TPS UI : Limited options should be available while doing state transition
Closed: Fixed None Opened 8 years ago by gkapoor.

Limited options should be available while doing state transition.
Let us suppose we are doing state transition from permanent lost.Currently in
drop down it shows all options.

Screenshot attached ::

image1 --> Gives http error code 500 when state change is not allowed
image2 --> All the options visible in drop down.Do we need to disable those
options??

Steps to Reproduce:

1. Install tps UI.Create a token
2. change state of token from perm_lost to active
3. HTTP error pop-up 500.

Actual results:

1. Seeing a HTTP 500 error code.(this comes when server is not able to fulfill
client request but not sure what error code it should throw) but error message
is correct.
2. In CS 8,it is grayed-out and a user can't pick those options.

Expected results:

Need to check with dev team.I believe two ways of handling it:

1. Raise correct error code with error message.
2. Disable all the extra state options like from permanetly lost we cann't go
to "active" so don't have that state in drop-down menu.

Additional info:

Created screenshot attachment 1088481 attached to associated bug

Per CS/DS meeting of 11/02/2015: 10.3

Fixed in master:

  • ce872456a09f5c5d146c6cb465b2466ad3ddc73d
  • 86a9bb86f36edc9922e864b3e0bdc76af8bb5812

The UI now will only display the valid transitions from the current state. Changing to an invalid state (e.g. via CLI) now will generate a BadRequestException (HTTP Error 400).

Additional fix in master:

  • 938c5ce2485b203bd55fc28f7bb4aa3f0151c429

Metadata Update from @gkapoor:
- 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/2243

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