Lesson plan

EJBCA

EJBCA (Enterprise JavaBeans Certificate Authority) is a free and open-source public key infrastructure (PKI) and certificate authority software package originally maintained and sponsored by the Swedish for-profit company PrimeKey Solutions AB, which holds the copyright to most of the codebase, and is now a part of Keyfactor Inc. based in the United States. The project's source code is available under the terms of the GNU Lesser General Public License (LGPL). The EJBCA software package is used to install a privately operated certificate authority, validation authority and registration authority. This is in contrast to commercial certificate, validation and/or authorities that are operated by a trusted third party. Since its inception EJBCA has been used as certificate authority software for different use cases, including eGovernment, endpoint management, research, energy, eIDAS, telecom, networking, and for usage in SMEs.

Back to article

Article summary

EJBCA (Enterprise JavaBeans Certificate Authority) is a free and open-source public key infrastructure (PKI) and certificate authority software package originally maintained and sponsored by the Swedish for-profit company PrimeKey Solutions AB, which holds the copyright to most of the codebase, and is now a part of Keyfactor Inc. based in the United States. The project's source code is available under the terms of the GNU Lesser General Public License (LGPL). The EJBCA software package is used to install a privately operated certificate authority, validation authority and registration authority. This is in contrast to commercial certificate, validation and/or authorities that are operated by a trusted third party. Since its inception EJBCA has been used as certificate authority software for different use cases, including eGovernment, endpoint management, research, energy, eIDAS, telecom, networking, and for usage in SMEs.

Key claims

No claims recorded.

Discussion questions

  1. Summarise the article in your own words. Which single claim would you verify first, and why?
  2. Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
  3. If two sources disagreed about one of these facts, what would you need in order to trust one over the other?

Bibliography

No sources recorded.

Key claims and bibliography are generated from the same tracked claims and sources as the article page.