+++ This bug was initially created as a clone of Bug #2047287 +++

Created attachment 1857112 [details]
Expected_behaviour_on_the_UI

Description of problem:
None of the tokens are visible on the TPS UI Page.

Version-Release number of selected component (if applicable):
[root@pki1 ~]# rpm -qa | grep pki
redhat-pki-tks-10.12.4-2.module+el8pki+14018+adf6c54d.noarch
redhat-pki-javadoc-10.12.4-2.module+el8pki+14018+adf6c54d.noarch
redhat-pki-symkey-10.12.4-2.module+el8pki+14018+adf6c54d.x86_64
redhat-pki-ca-10.12.4-2.module+el8pki+14018+adf6c54d.noarch
redhat-pki-10.12.4-2.module+el8pki+14018+adf6c54d.x86_64
redhat-pki-base-java-10.12.4-2.module+el8pki+14018+adf6c54d.noarch
redhat-pki-ocsp-10.12.4-2.module+el8pki+14018+adf6c54d.noarch
redhat-pki-base-10.12.4-2.module+el8pki+14018+adf6c54d.noarch
redhat-pki-kra-10.12.4-2.module+el8pki+14018+adf6c54d.noarch
redhat-pki-tools-10.12.4-2.module+el8pki+14018+adf6c54d.x86_64
redhat-pki-tps-10.12.4-2.module+el8pki+14018+adf6c54d.x86_64
pki-servlet-4.0-api-9.0.30-3.module+el8.5.0+11388+9e95fe00.noarch
redhat-pki-server-10.12.4-2.module+el8pki+14018+adf6c54d.noarch
redhat-pki-server-theme-10.12.4-2.module+el8pki+14018+adf6c54d.noarch
python3-redhat-pki-10.12.4-2.module+el8pki+14018+adf6c54d.noarch
pki-servlet-engine-9.0.30-3.module+el8.5.0+11388+9e95fe00.noarch
redhat-pki-acme-10.12.4-2.module+el8pki+14018+adf6c54d.noarch

How reproducible:
Always

Steps to Reproduce:
1. Format and Enroll a token via tpsclient or just add a token via Web UI.

Actual results:
None of the tokens are visible on the TPS Web UI.

Expected results:
The new tokens should be visible on the TPS Web UI.

Additional info:
Tokens are visible on the older bits: 10.12.1-1 but not on the latest 10.12.4-2.
Debug logs are showing the entries getting recorded successfully but the entries aren't visible on the UI.

— Additional comment from Endi Sukma Dewata on 2022-01-27 15:08:09 UTC —

Is there any error in the browser's JavaScript console?

— Additional comment from on 2022-01-27 15:48:00 UTC —

(In reply to Endi Sukma Dewata from comment #1)
> Is there any error in the browser's JavaScript console?

Yes, there is an error in the console.

It shows "Uncaught ReferenceError: respModifyTimestamp is not defined".

Let me know if I can provide you with more info for your reference.

— Additional comment from on 2022-01-28 02:03:00 UTC —

The "tps-token-find" CLI is working as expected, it lists all the tokens properly.

[root@pki1 ~]# pki -d /opt/pki/certdb/ -c SECret.123 -p 25443 -n 'PKI TPS Administrator for Example.Org' tps-token-find
-----------------
2 entries matched
-----------------
Token ID: 123456789
User ID: Test_Token_ID
Status: UNFORMATTED
Next States: DAMAGED, PERM_LOST
Policy: Test_Token_Policy
Date Created: Thu Jan 27 20:58:13 EST 2022

Token ID: 40906145C76224192D2B
User ID: jdoe
Type: userKey
Status: ACTIVE
Next States: DAMAGED, PERM_LOST, SUSPENDED, TERMINATED
Applet ID: 1.4.58768072
Key Info: 0101
Policy: RE_ENROLL=YES;RENEW=NO;FORCE_FORMAT=NO;PIN_RESET=NO;RESET_PIN_RESET_TO_NO=NO
Date Created: Thu Jan 27 14:18:40 EST 2022
Date Modified: Thu Jan 27 14:21:59 EST 2022
----------------------------
Number of entries returned 2
----------------------------

— Additional comment from Chris Kelley on 2022-01-28 07:54:25 UTC —

Sigh, this is probably because of an issue in rolling back code in attempting to fix bug 1984455.

Apologies for this, I checked the files with diff before and after reverting to make double-sure I had put it back exactly. I don't understand how I've managed to break this (again)- I'll have another look.

— Additional comment from Chris Kelley on 2022-02-15 17:29:26 UTC —

Assigning to Chris for investigation.

— Additional comment from RHEL Program Management on 2022-02-15 17:29:33 UTC —

The certsys-10.3 release flag is set to + as well as all required acks set to + for this bug because the target release is certsys-10.3 and the bug is in ASSIGNED, MODIFIED or POST state.