You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When formatting an unknown token, TPS will implicitly add the token into the database in addition to formatting the token. However, currently TPS will only log the format operation, the add operation is not recorded in the activity log.
Similarly, when enrolling an unknown token, TPS will only log the enrollment operation, the implicit add and format operations are not logged.
Ideally TPS should record the complete lifecycle of the token, so the above operations should generate the following logs:
formatting unknown token: add, format
enrolling unknown token: add, format, enrollment
The text was updated successfully, but these errors were encountered:
Note that if the allowed transaction list does not include UNFORMATTED -> FORMATTED transition, the unknown token should still be added successfully (and logged), but it will fail to format.
One odd behavior was observed, which I filed a separate bug for: https://fedorahosted.org/pki/ticket/2354 [TPS] missing activity log entries via UI and CLI (while correctly recorded in LDAP)
This issue was migrated from Pagure Issue #2335. Originally filed by edewata (@edewata) on 2016-05-19 00:25:26:
When formatting an unknown token, TPS will implicitly add the token into the database in addition to formatting the token. However, currently TPS will only log the format operation, the add operation is not recorded in the activity log.
Similarly, when enrolling an unknown token, TPS will only log the enrollment operation, the implicit add and format operations are not logged.
Ideally TPS should record the complete lifecycle of the token, so the above operations should generate the following logs:
The text was updated successfully, but these errors were encountered: