In Dogtag 10.3 some invalid token transitions (e.g. UNINITIALIZED to ACTIVE) were removed from CS.cfg and the labels for the valid token transitions are now stored in token-states.properties. If an older TPS was upgraded to Dogtag 10.3, the CS.cfg will still contain the old invalid transitions, and the UI will fail to find the labels for those transitions in token-states.properties, generating a MissingResourceException.

One option is to write an upgrade script to remove the invalid transitions from CS.cfg. This may change the server behavior, so this will not be acceptable if the user relies on the old invalid transitions.

Another option is to add the labels for the old transitions into the token-states.properties even though they are invalid (e.g. "This uninitialized token has been activated"). The invalid transitions will appear in the UI and it will be selectable like other valid transitions.

Another option is to generate the label dynamically for any transition that doesn't exist in token-states.properties (e.g. "Change UNITIALIZED to ACTIVE"). In this case the invalid transitions will also appear in the UI.