EJBCA: Difference between revisions
No edit summary |
No edit summary |
||
| Line 22: | Line 22: | ||
'''EJBCA''' is a [[open source|Open source]], [[Platform_independent|platform independent]], feature-rich, fully [[Computer_cluster|clusterable]] [[Certificate_authority|CA]] solution implemented in [[Enterprise_Java|Enterprise Java]]. A full list of features are available [http://www.ejbca.org/features.html#Features here]. |
'''EJBCA''' is a [[open source|Open source]], [[Platform_independent|platform independent]], feature-rich, fully [[Computer_cluster|clusterable]] [[Certificate_authority|CA]] solution implemented in [[Enterprise_Java|Enterprise Java]]. A full list of features are available [http://www.ejbca.org/features.html#Features here]. |
||
| ⚫ | |||
For updated and reliable information, please visit the project website. |
|||
| ⚫ | |||
==Scalability== |
==Scalability== |
||
| Line 30: | Line 31: | ||
Massive installations use multiple instances of EJBCA running on a [[Computer_cluster|cluster]], a fully distributed database on a separate cluster and a third cluster with [[Hardware_Security_Module|HSMs]] keeping the different CA keys. This configuration is also useful when deploying EJBCA as a heavy-load [[Ocsp|Online Certificate Status Protocol (OCSP)]] responder cluster. |
Massive installations use multiple instances of EJBCA running on a [[Computer_cluster|cluster]], a fully distributed database on a separate cluster and a third cluster with [[Hardware_Security_Module|HSMs]] keeping the different CA keys. This configuration is also useful when deploying EJBCA as a heavy-load [[Ocsp|Online Certificate Status Protocol (OCSP)]] responder cluster. |
||
| ⚫ | |||
| ⚫ | |||
==Developing EJBCA== |
==Developing EJBCA== |
||
Revision as of 10:08, 29 April 2008
This article may meet Wikipedia's criteria for speedy deletion because in its current form it serves only to promote or publicise an entity, person, product, or idea, and would require a fundamental rewrite in order to become encyclopedic. However, the mere fact that a company, organization, or product is a page's subject does not, on its own, qualify that page for deletion under this criterion. This criterion also does not apply where substantial encyclopedic content would remain after removing the promotional material as deletion is not cleanup; in this case please remove the promotional material yourself, or add the {{advert}} tag to alert others to do so. See CSD G11.
If this article does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message. Note that this article may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Note to administrators: this article has content on its talk page which should be checked before deletion. Administrators: check links, talk, history (last), and logs before deletion. Consider checking Google.This page was last edited by ZeiZai6Y (contribs | logs) at 10:08, 29 April 2008 (UTC) (16 years ago) |
 | This article may be too technical for most readers to understand. |
| Developer(s) | List of developers |
|---|---|
| Initial release | November 30, 2001 |
| Stable release | 3.6.0
/ April 6, 2008 |
| Repository | |
| Written in | JAVA, J2EE |
| Operating system | Cross-platform |
| Available in | Chinese, English, French, German, Italian, Portuguese, Spanish, Swedish |
| Type | PKI Software |
| License | LGPL |
| Website | www.ejbca.org EJBCA at SourceForge |
EJBCA is a Open source, platform independent, feature-rich, fully clusterable CA solution implemented in Enterprise Java. A full list of features are available here.
The name
EJBCA stands for Enterprise Java Bean Certificate Authority.
Scalability
Each EJBCA instance is running inside an application server sharing a database with other instances. The references to all the certificate authorities (CAs) exist in the database, so all the instances of EJBCA can use any CA if the keys are available. If the keys are kept in a Hardware Security Module (HSM) each instance also has to be able access the HSM.
The simplest possible example uses the built-in database Hypersonic in the JBoss Application Server on a single node with soft private keys in the database.
Massive installations use multiple instances of EJBCA running on a cluster, a fully distributed database on a separate cluster and a third cluster with HSMs keeping the different CA keys. This configuration is also useful when deploying EJBCA as a heavy-load Online Certificate Status Protocol (OCSP) responder cluster.
Developing EJBCA
The EJBCA sourcecode comes with project files for the Eclipse IDE. CVS version control has been dropped in order to make way for SVN.