1 <?xml version=
"1.0" encoding=
"iso-8859-1"?>
2 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns=
"http://www.w3.org/1999/xhtml" lang=
"en" xml:
lang=
"en">
5 <title>OpenXPKI Project - Features and requirements
</title>
6 <link rel=
"stylesheet" title=
"default" href=
"../css/openxpki.css" type=
"text/css" />
7 <meta http-equiv=
"Content-Type" content=
"text/html; charset=iso-8859-1" />
16 <img src=
"../images/openxpki_logo.png"
17 alt=
"OpenXPKI Project"/>
20 </div> <!-- header -->
24 <div class=
"menu_item"><a href=
"..">Home
</a></div>
25 <div class=
"menu_item"><a href=
"index.html">Features
</a></div>
26 <div class=
"menu_item"><a href=
"../secadvs/index.html">Security Advisories
</a></div>
27 <div class=
"menu_item"><a href=
"../news/index.html">News
</a></div>
28 <div class=
"menu_item"><a href=
"../docs/index.html">Documentation
</a></div>
29 <div class=
"menu_item"><a href=
"../support/index.html">Support
</a></div>
30 <div class=
"menu_item"><a href=
"../download/index.html">Download
</a></div>
31 <div class=
"menu_item"><a href=
"http://wiki.openxpki.org">Wiki
</a></div>
32 <div class=
"menu_item"><a href=
"../resources/index.html">Resources
</a></div>
33 <div class=
"menu_item"><a href=
"../foundation/index.html">Foundation
</a></div>
34 <div class=
"menu_item"><a href=
"../legacy/index.html">OpenCA Legacy
</a></div>
36 <a href=
"http://sourceforge.net"><img src=
"http://sflogo.sourceforge.net/sflogo.php?group_id=150124&type=1" width=
"88" height=
"31" alt=
"SourceForge.net Logo" /></a>
39 <a href=
"http://validator.w3.org/check?uri=http://www.openxpki.org/features/index.html"><img class=
"noborder" src=
"../images/valid-xhtml10.png" alt=
"Valid XHTML 1.0!" height=
"31" width=
"88" /></a>
42 <a href=
"http://www.masonhq.com/"><img class=
"noborder" src=
"../images/built-with-white1.png" alt=
"Built with Mason" height=
"31" width=
"88" /></a>
51 <h2>OpenXPKI features and requirements
</h2>
53 OpenXPKI makes a few assumptions about its operating environment. You
54 will need some infrastructure components to make it work properly.
57 <h3>Operating environment
</h3>
58 <h4>Supported operating systems
</h4>
60 OpenXPKI runs on most Unix-like operating systems that use the Unix
61 process model and provide a POSIX environment.
62 It has been successfully tested on
65 <li>Linux (tested on Debian GNU/Linux and SuSE SLES)
</li>
66 <li>Mac OS X (tested on
10.4 and
10.5)
</li>
67 <li>Sun Solaris and OpenSolaris (tested on version
10 of both)
</li>
70 Because of some assumptions about the process environment it will
71 <b>not
</b> run natively under Microsoft Windows.
74 <h4>Supported databases
</h4>
76 OpenXPKI requires a relational database for operation. Drivers are
84 (Adding support for databases not mentioned here should be possible if a
85 Perl DBD driver module exists for this particular database.
86 At a minimum, the database must support multiple concurrent
87 connections (ruling out SQLite for production use) and transaction support.)
90 <h4>Request tracking
</h4>
92 OpenXPKI provides built-in integration with the
93 <a href=
"http://bestpractical.com/rt/">RT Request Tracker
</a>. It
94 can automatically create and link tickets in the RT system for
95 incoming certificate requests and thus allows Registration Officers
96 to keep track of their workload.
100 <h3>Key features
</h3>
102 <h4>Multiple CA instances
</h4>
104 OpenXPKI supports the configuration of multiple independent logical PKIs
105 (
"PKI Realms") in one single application instance. This allows for
106 configuration e. g. of a Root CA and one or more subordinate CAs within
107 one single installation.
110 <h4>Fully automatic CA rollover
</h4>
112 Within a logical PKI (PKI Realm) OpenXPKI provides the possibility
113 to configure multiple Issuing CAs with overlapping validity.
114 Once a new Issuing CA becomes valid it takes over for issuing new
115 certificates. This unique feature allows for a fully automatic
116 CA rollover where administrators do not have to take down and
117 reconfigure the whole PKI installation once a CA certificate is about
121 <h4>Highly customizable
</h4>
123 Instead of hard-wiring the interface and the PKI operations in a monolithic
124 application, OpenXPKI utilizes a workflow engine that allows to
125 easily modify and extend the basic operation of the PKI (e. g.
126 certificate request and approval). Customizing the behaviour of the
127 system is often accomplished by simply modifying the workflow description
131 In addition the workflow engine makes it possible to extend the
132 system with customized workflows.
135 <h4>Hardware Security Module support
</h4>
137 Critical cryptographic operations such as Digital Signatures can be
138 performed via a Hardware Security Module. Currently OpenXPKI supports
139 nCipher nShield modules.
141 </div> <!-- content -->
144 Last modified by svysh on Mon Jan
26 10:
36:
27 UTC
2009
145 (based on rev.
1360).
© 2005 -
2008 OpenXPKI Foundation
148 </div> <!-- footer -->