dogtagpki

#672 Investigate rewriting TPS in Java vs. reuse existing code
Closed: Fixed Opened by edewata.

Closed: Fixed
Reopen Issue

This is a continuation of ticket #526.

We should investigate moving TPS from httpd to Tomcat. We want to do some cleanup and refactoring of the TPS code anyway, and it might just make more sense to port it to Java and use Tomcat like most of the other Dogtag subsystems.

Things we specifically need to look at are:

  • Are we able to share existing shared Java code with the other subsystems (allowing us to get rid of things we have duplicated in C just for TPS)?
  • Compare the effort of cleaning up our existing C code vs. rewriting in Java.

We should look at all other functionality we are looking at adding to TPS and take that into account when deciding the approach to take. If we would have to rewrite large portions of TPS to implement new features, it might just be better to move to Java/Tomcat? at the same time.

It was decided that the TPS token database will be rewritten completely in Java, and the rest of TPS will be converted as much as possible into Java. This will be an on going effort.

Metadata Update from @edewata:
- Issue set to the milestone: 10.1 - 07/13 (July)

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

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
None
Normal
defect
TPS
Community
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.