TPS UI: Token change status operation, transition from Uninitialized to Active is successful but no cert found for the token under certificates

[pki-bot]

This issue was migrated from Pagure Issue #1275. Originally filed by mharmsen (@mharmsen) on 2015-02-25 02:03:34:

• Closed as Fixed
• Assigned to edewata (@edewata)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1195398

---

TPS UI: Token change status operation, transition from Uninitialized to Active
is successful but no certificate found for the token under certificates

How reproducible:

always

Steps to Reproduce:

1. Format an Uninitialized token
2. From the UI, select the token in Uninitialized state
3. Change the status from Uninitialized to Active

Actual results:

This change is successful but cannot find any certificates for the token under
the Certificates tab of the UI

Expected results:

Change status from Uninitialized to Active should not be allowed. Uninitialized
to Active should happen only after enrollment of the token.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-02-27 01:56:12

Per 10.2.3 Triage meeting of 02/26/2015: 10.2.3

[pki-bot]

Comment from jmagne (@jmagne) at 2015-03-03 04:02:12

OK, I know what is going on here.

There are two types of states, UI states and operations states.

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

The preceding allowedTransitions (UI transtions) has the one 0:4 which is "unitialized" to "FOUND".

This should probably not be in the list. Also the UI calls this transition "ACTIVE". ACTIVE is really an operation transition that has the same number as FOUND, which is set with the UI.

Two things to fix this. Take out the 0:4 transition from the UI transistion list. Also change the name of the state to "FOUND" in the UI.

When a formatted token is enrolled with the server its state goes from 0 "unitialized" to 4 "active".

[pki-bot]

Comment from edewata (@edewata) at 2015-04-21 03:29:15

Moving to 10.2.4 per CS team meeting.

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-04-28 20:41:23

Per Dogtag 10.2.x TRIAGE meeting of 04/28/2015: (Tech Preview Feature)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-06-08 20:52:45

Per CS/DS meeting of 06/08/2015: 10.2.6

[pki-bot]

Comment from mharmsen (@mharmsen) at 2015-06-30 20:43:05

Per Dogtag 10.2.6 TRIAGE meeting of 06/30/2015: 10.3

[pki-bot]

Comment from edewata (@edewata) at 2015-11-04 02:54:26

This requires:

• fixing the configuration as described in comment 3
• writing an upgrade script
• updating the labels in the UI

[pki-bot]

Comment from edewata (@edewata) at 2016-02-05 18:33:41

Fixed in master:

• ce87245

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-02-27 13:59:58

Metadata Update from @mharmsen:

• Issue assigned to edewata
• Issue set to the milestone: 10.3.0