Difference between revisions of "PKI Roadmap"

From Dogtag
Jump to: navigation, search
(Next Steps)
(Next Steps)
Line 26: Line 26:
 
* Fine-tune TPS and ESC interaction for handling the lost key scenario
 
* Fine-tune TPS and ESC interaction for handling the lost key scenario
 
* Support Failover/Cloning everywhere including TPS
 
* Support Failover/Cloning everywhere including TPS
 +
* Verify that Dogtag supports IPv6

Revision as of 22:02, 13 April 2008

Team, History, and Contributors

Initial Release

Next Steps

This is a community-based project. Your ideas matter and it will shape our roadmap. Please add your ideas to the Wishlist.

  • Allow tomcatjss to be provided as part of the operating system
  • Integrate the osutil and symkey JNI components into jss (which is also a JNI component), and change the jss RPM to provide osutil and symkey functionality so that these two stand-alone packages can be retired
  • Provide an inventory and descriptions of all of the various tools present in this PKI
  • Provide some real world use cases for this product
  • Update the code to use newer JDK1.5+ features
  • Make certificate enrollment, renewal dead easy with other products such as Apache, tomcat
  • Simplify the configuration, and provide more detailed documentation in this area
  • Provide greater detail on the use of pkisilent
  • Clarify development practices including how to remove PKI instances and subsystems
  • Provide clean XML-based external interface
  • Enhance Performance in enrollment and CRL generation
  • Update user, agent interfaces to use Ajax-style navigation
  • Merge TPS agent interface with the security officer interface
  • Fine-tune TPS and ESC interaction for handling the lost key scenario
  • Support Failover/Cloning everywhere including TPS
  • Verify that Dogtag supports IPv6