dogtagpki

#1049 Add method to generate TPS activity ID
Closed: Fixed Opened by edewata.

Closed: Fixed
Reopen Issue

The ActivityDatabase was originally written as a persistence layer and it was expecting the activity ID to be supplied by the caller. A new method should be added to generate the activity ID based on the following code in tus_db.c:1931:

  ct = PR_GetCurrentThread();
  now = PR_Now();
  PR_ExplodeTime(now, PR_LocalTimeParameters, &time);
  /* unique id per activity */
  PR_snprintf(zcdate, 256, "%04d%02d%02d%02d%02d%02d%06d.%x",
              time.tm_year, (time.tm_month + 1), time.tm_mday,
              time.tm_hour, time.tm_min, time.tm_sec, time.tm_usec, ct);

master: 0b4f4e78841abdb9ab90c7b084ddfe89f4043743

Metadata Update from @edewata:
- Issue assigned to edewata
- Issue set to the milestone: 10.2 - 06/14 (June)

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/1614

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.
Metadata
None
None
None
Normal
defect
TPS
Community
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.