Keyfactor Days 2027 – Participez à la conférence « Trust Security » à San Diego Inscrivez-vous dès maintenant !

25 Years of Trust: How EJBCA Keeps Moving Forward

Tomas Gustavsson Tomas Gustavsson Chief PKI Officer
25 Years of Trust: How EJBCA Keeps Moving Forward

When someone asks what EJBCA turning 25 means to me, my first thought is that I’m getting old.

After that, I can take a moment to be proud. Something I started as an educational project has become an enterprise-grade platform that people around the world continue to find useful. Along the way, it has brought together people whose ideas and care have kept it moving forward.

That is what we are celebrating at Keyfactor: 25 years of building, listening, and adapting. Every team member, user, and contributor who has helped shape EJBCA has a part in that story.

A small project with enterprise ambitions

EJBCA began partly because I wanted to learn more about the Java enterprise platform I was working with. But there was also a practical problem to solve.

At the time, public key infrastructure (PKI) projects had a reputation for being large, expensive, and difficult to deliver. The software could be cumbersome, with limitations around performance and scalability. I wanted to make PKI more accessible and give organizations a more nimble way to build it.

Even as a personal project, EJBCA was designed with enterprise needs in mind. Scalability, performance, and high availability were considerations from the beginning. There was a deliberate architecture behind it, giving us a foundation we could continue to develop.

Making it open source felt natural. I had benefited from other people’s open source work and wanted to contribute something in return. EJBCA depended on Bouncy Castle for cryptographic capabilities that Java itself did not provide at the time. Building on that community’s work made me want to be part of it.

The people who showed us what came next

Early users began picking up EJBCA for serious purposes and contributing improvements. That was an important confirmation: other people had seen the same gap and wanted something that could fill it.

As adoption grew, large enterprises and government organizations asked us to help put EJBCA into demanding environments. Their requirements pushed us to improve scalability and security. Listening to those organizations helped turn the original architectural ambitions into capabilities people could rely on.

That relationship has continued throughout EJBCA’s history. Open source users, commercial customers, and contributors have helped us understand which features matter and where the product needs to go. The broader software community has influenced us, too. Bouncy Castle and the other open source projects we depend on have evolved alongside us, opening up new possibilities.

Today, Keyfactor EJBCA serves a breadth of uses I could not have imagined at the start, from highly restricted government environments to commercial and consumer products. Even now, I only see glimpses of all the ways people use it.

Keeping the foundation while modernizing

Over 25 years, we have had plenty of opportunities to choose a different technical direction. We stayed with Java Enterprise, now Jakarta EE, and modernized alongside a platform designed for demanding enterprise environments. Other paths might also have worked, but this one has supported continuity as the product has grown.

Continuity has still required significant change. Work on Common Criteria certification in 2012 prompted important security architecture decisions. Mike Kushner played a key role in that work, helping build layered protections into the product. Later, collaboration with organizations embracing cloud infrastructure helped us expand into cloud and container environments.

Those changes took a willingness to explore new approaches while continuing to support existing deployments. Customers adopting new infrastructure needed us to move forward. Customers with established environments needed us to bring them along.

Agility includes the users already relying on you

One example of that commitment is upgradeability. It is possible to take an EJBCA version from roughly 20 years ago and work through an upgrade to the latest version. It will take more than five minutes, but there is a path.

Maintaining that path requires care for code quality, architecture, and the people operating the software. Our team has consistently treated those responsibilities as part of product development. As we continue that work at Keyfactor, innovation and customer care remain closely connected: new capabilities need to help users move forward.

The work ahead

Keyfactor EJBCA must keep modernizing. It needs to run on current platforms and use dependencies that can receive current security updates. That does not mean rewriting every line of code. It means continually doing the work that keeps the platform secure, useful, and ready for changing requirements.

I am proud that EJBCA has reached 25 while continuing to evolve. I am also grateful to everyone I have had the opportunity to work with along the way. Together, we have built something that has lasted because we have kept improving it. I look forward to continuing that work.

S'abonner à La Source

Stay secure with Keyfactor's monthly newsletter, packed with expert insights and practical steps for quantum-readiness.

Lire la suite

Conformité

Le cadre de référence SWIFT relatif aux contrôles de sécurité des clients : la cryptographie dans le cadre des relations de correspondance bancaire

En savoir plus
Conformité

The New FDA Cybersecurity Rules for Medical Devices: What Manufacturers Must Prove Before They Ship

En savoir plus
Conformité

Le chiffrement : un atout en matière de conformité au RGPD pour le secteur des services financiers

En savoir plus