EJBCA Enterprise Cloud Validation Authority (VA) - Premium Support

The main use case for EJBCA Enterprise in Dell PW is public key infrastructure and certificate lifecycle management. In simple terms, EJBCA Enterprise acts as a certificate authority that creates, signs, manages, and validates digital certificates used to establish trust between PW components and services. The main use cases involve certificate issuance and renewal before expiration. Keyfactor's jobs run daily to check for any expiring certificates and provide alerts if jobs fail, along with the status of certificates due for expiration.

For example, in a real-world enterprise scenario using Dell PW, a telecom company deploys a private 5G network for a large manufacturing plant with multiple services running on Kubernetes in AKS that need secure communication. Since the company does not want each application generating and managing its own certificate, EJBCA Enterprise becomes essential, acting as a certificate authority where a PW service needs certificates.

For example, Hermes needs a certificate to communicate securely with another PW service, with Keyfactor managing the certificate request and EJBCA Enterprise signing the certificates before deployment, which ensures secure communications between Hermes servers and clients.

We use EJBCA Enterprise in our PW enterprise application to establish secure communications between the Hermes client deployed on the client side and our Hermes server, which allows us to check and renew certificates.

The best features EJBCA Enterprise offers, in my opinion, include high availability and clustering, REST API and certificate automation, audit logging, role-based access control, and support for multiple CA and RA architectures.

In my day-to-day work, high availability and certificates have made the biggest difference.

EJBCA Enterprise has positively impacted my organization by improving security, reducing operational risk, and enhancing production reliability. This is particularly true in a large enterprise, where my application supports private wireless infrastructure and multiple interconnected services through secure connection establishment and certificate renewal.

Before automation, when we deployed across multiple environments such as dev, SIT, prod, and UAT, manually creating certificates took considerable time. With EJBCA Enterprise, we save almost three hours on customer-related tasks, create certificates faster, and reduce manual work for the testing teams.

EJBCA Enterprise could be improved in terms of certificate lifecycle management and error handling in Keyfactor jobs, which sometimes throw unclear error codes. More specific details should be provided for failures, along with enhanced security through more granular RBAC and approval policies, better searchable audit history, and reporting.

Unclear error codes when jobs fail are a frustration for me.

I have been using EJBCA Enterprise for four and a half years.

EJBCA Enterprise is stable.

EJBCA Enterprise provides excellent scalability, supporting large-scale certificate management, multiple CA configurations, clustering, and high availability deployments. It is capable of scaling to accommodate an increasing number of application services and infrastructure components.

Customer support is reliable and responds promptly depending on the severity of the issues raised, especially if they impact production.

I would rate customer support as a 10.

I do not believe we have used any different solutions. We have always started with EJBCA Enterprise and Keyfactor.

EJBCA Enterprise was first deployed on Azure AKS clusters. Last year, we deployed EJBCA Enterprise and Keyfactor in-house, which means we have a mixed deployment in our organization.

We exclusively use Azure for our deployments.

We see potential operational benefits from EJBCA Enterprise through centralized certificate management, improved security, reduced manual handling activities, and increased operational reliability through fewer manual renewals needed.

Pricing, setup costs, and licensing are not handled by us, as they are managed by higher management in our large organization.

Before choosing EJBCA Enterprise, we evaluated other PKI and certificate authority solutions such as Microsoft AD CS, HashiCorp Vault PKI, and OpenSSL-based solutions. We evaluated them based on security, scalability, and certificate lifecycle management before deciding to go with EJBCA Enterprise.

I would rate EJBCA Enterprise as a seven on a scale of 1 to 10.

I chose seven due to its strong certificate authority, PKI management, HSM integration, high availability, rapid customer support response, and the areas for improvement I have already shared.

Regarding EJBCA Enterprise's AI capabilities, we handled a project deploying in the US government port on Azure AKS clusters where security was well maintained. Although the project is not live yet, I feel EJBCA Enterprise handles security effectively, and I distinguish between its secure capabilities and its AI capabilities, though I cannot confirm deployment specifics.

I advise others looking into using EJBCA Enterprise to acknowledge how it reduces human effort, enhances security, and provides high availability while evaluating certificate management requirements and integration with existing infrastructure before implementation.

Our main use case for EJBCA Enterprise is internal certificate management.

t.

The best features EJBCA Enterprise offers include user-convenient management system, along with detailed profiles for certificate management.

Vault integrations and PQC enablement stand out for me.

Include templated profiles for compliance-based certificates. Additional improvements needed for EJBCA Enterprise include pushing more services to SaaS with PQC enablement.

We have been using EJBCA Enterprise for the last four years to manage our PKI system.

EJBCA Enterprise is stable.

EJBCA Enterprise's scalability is positive, and it is easily scalable, even with respect to certificate growth.

The customer support for EJBCA Enterprise is good, and while there can be delays sometimes due to representatives not fully understanding the system, the overall turnaround time is fast.

I rate the customer support as eight.

No

I have not evaluated the return on investment in detail, but my impression is that we save time and need fewer employees for certain tasks.

I would not say it is too costly, but I believe the pricing is on the higher side, justified by the user convenient portals and proactive support system.

We evaluated couple of market leaders

I gave EJBCA Enterprise a nine due to room for improvement, as not every user who will operate the system is tech-savvy.

My advice for others considering EJBCA Enterprise is to proceed if they have assessed the technical compatibility and use cases required.

My main use case for EJBCA Enterprise is the creation, registering, and verification of certificates for MFA.

I work for an IAM organization where I use EJBCA Enterprise for browser verification of a device or the device itself, and for that we use the certificates.

I use EJBCA Enterprise to create self-signed certificates for multiple organizations, as many customers who are contracted want to create their self-signed certificates.

Since using EJBCA Enterprise, I see my organization becoming more upgraded and easier to use, and the console is significantly better now.

It is time-saving; earlier it used to take me more than four or five minutes to create a certificate and its intermediate certificate, but now within two or three minutes I can create the root and certificate if I have the attributes available.

The best features EJBCA Enterprise offers, in my opinion, are its superior security compared to some other MFAs which are not anti-phishing.

When I say it is better in terms of security, I mean that for a phone, if you are using a cell phone as MFA, it is not necessary that you always have your cell phone with you, but the certificates are always installed in your browser, and you just have to match the certificate when you are trying to log in. Multiple users can install the certificate in the same device or in the same browser.

I have always used EJBCA Enterprise for security itself.

EJBCA Enterprise could be improved because when I started with EJBCA, I did not have many useful courses for creating an intermediate certificate.

Documentation for EJBCA Enterprise is getting better, but there are still some improvements needed to verify each and every tag used in EJBCA Enterprise console, and better descriptions could also help.

I choose a rating of eight because EJBCA Enterprise console takes a lot of time to load and keeps buffering when I click on a certain link.

I have been using EJBCA Enterprise for more than a year.

EJBCA Enterprise is stable in my experience.

The scalability of EJBCA Enterprise was not that good earlier, but now it is better.

EJBCA Enterprise was my first choice; I did not use a different solution before.

I believe the time-saving aspect of using EJBCA Enterprise is valuable; I appreciate it in terms of MFA, and it does save money because using alternatives such as Twilio or other MFA options is more cost-efficient and handy.

I did evaluate other public infrastructure options before choosing EJBCA Enterprise; I think one was related to Microsoft, but I find EJBCA Enterprise better.

I would rate EJBCA Enterprise an eight overall.

I think EJBCA Enterprise is doing a great job regarding its AI capabilities, and I believe they should keep implementing it.

I find EJBCA Enterprise's accuracy and reliability of output to be good, though it depends on the prompts a person gives.

I would advise others looking into using EJBCA Enterprise to make the console faster, as it takes a lot of time for the request-response cycle.

EJBCA Enterprise is particularly valuable for certificate lifecycles and can definitely be used for automating the certificate lifecycle. If an organization is in a large enterprise or a big telecom company, EJBCA Enterprise can help automate and centralize certificates. For example, if an organization has a large number of servers or networking devices, manually managing certificates becomes very difficult, and EJBCA Enterprise helps automate certificate issuance, renewal, and revocation, making it easier to maintain trust across the infrastructure.

One of the most important pain points in certificate life management is that certificates have defined validity periods, so they need to be issued correctly, renewed before their expiration time, and revoked in case of any compromise or when someone is no longer trusted. When these processes are handled manually, it becomes very difficult to maintain all these different certificates together. From my exposure, I understand that this matters in an enterprise and telecom environment where systems need to communicate securely and reliably, and certificate trust is an important part of EJBCA Enterprise.

EJBCA Enterprise has definitely impacted my organization positively by combining security controls and automation in certificate management.

The security teams definitely need to understand what certificates have been issued, which certificate authority is responsible for them, and whether the certificate management activities follow the organization's policies. EJBCA Enterprise helps the team in those fields.

In my opinion, the most valuable feature EJBCA Enterprise offers is the certificate lifecycle automation, which has been discussed at a great scale. It is obviously scalable and flexible when trying to integrate with different teams and enterprise infrastructures, and this scalability is really important in an enterprise or bigger environment. The number of devices, applications, and services can grow exponentially, and if an organization has to manage this manually, it would be very difficult and would definitely result in some issues. The automation and scalability of EJBCA Enterprise is definitely one of the biggest standout features.

It is important when systems depend on secure communication and trusted identities that certificate management has a direct impact on both security and operational reliability. Even though the automation and scalability are important, they definitely impact security and how trusted communications are handled in an enterprise.

The biggest benefit of having a strong PKI control system is improved consistency and traceability. During my internship, I had some exposure to security testing and the importance of validating. I see that auditability is another major benefit that EJBCA Enterprise has. I would focus on making certificate lifecycle management easier to understand, improving operational visibility, and simplifying integrations so that teams with limited experience can help integrate EJBCA Enterprise in the environment.

Troubleshooting and observability can be made more accessible. When a certificate-based connection fails, the cause may be an expired certificate, an incomplete trust chain, or an incorrect certificate. If more context is provided, EJBCA Enterprise can be improved.

I used EJBCA Enterprise during an internship for cyber security activities where I became familiar with the role of PKI, particularly in the context of digital certificates and certificate-based trust for securing communications.

I have had exposure to EJBCA Enterprise in the context of my cyber security internship, and my familiarity is with PKI concepts, digital certificates, and secure communication. I have familiarity from practical work during the internship where I learned about the role EJBCA Enterprise plays in maintaining certificate authorities and certificate lifecycles. I am happy to discuss those things and the technical aspects required for my area of expertise.

EJBCA Enterprise is stable for the processes that need to be completed, including the automation and certificate management, and all of those have been pretty stable.

EJBCA Enterprise is quite scalable for different environments and different enterprises. As I mentioned, it is definitely pretty scalable in telecom as well.

I would currently give EJBCA Enterprise a rating of seven or eight, and if the mentioned improvements can be applied, it will help EJBCA Enterprise be much more flexible and scalable.

I chose a seven or eight for my rating because, as I mentioned, the integrations should be much easier and the troubleshooting for certificate management needs improvement. If those tips I provided on how to improve EJBCA Enterprise are applied, the rating would definitely go higher.

If other organizations are planning to use EJBCA Enterprise, they should definitely look into some important factors.

My main use case for EJBCA Enterprise is to provide certificates to all the radio and network related devices and to enjoyment machines and all other devices.

A specific example of a device where I used EJBCA Enterprise to provide certificates includes radios, switches, antennas, mobile devices, and domain-joined Windows machines.

These were the cases where EJBCA Enterprise stood out, and I also sometimes used it for email signing certificates.

EJBCA Enterprise has positively impacted my organization by providing ease of use. It got integrated with Keyfactor to supply all the other domain-joined machine certificates as well.

It made things easier by saving my team time, reducing errors, and improving security in a noticeable way.

The best features of EJBCA Enterprise include having a very good platform to use while utilizing it in Kubernetes.

What I find especially valuable about using EJBCA Enterprise in Kubernetes is the scalability and to some extent the deployment process as well.

Additionally, the user interface was quite good, and EJBCA Enterprise has the capability to include the RA, CA, root CA, and sub-CA in the single interface as well.

The user interface looked quite orthodox and could be improved a little bit.

I have been using EJBCA Enterprise for one year.

I would rate EJBCA Enterprise a nine out of ten.

I chose nine out of ten due to some improvements that are needed.

My advice to others looking into using EJBCA Enterprise is that if their end users are devices such as radios, antennas, and switches and their base platform is Kubernetes, they should preferably switch to EJBCA Enterprise for easy deployment.

My main use case for EJBCA Enterprise involves managing and maintaining the complete lifecycle of certificates and addressing client needs while maintaining the PKI and CA certificates, ensuring all CA certificates and end user certificates comply with our internal security requirements and legal obligations regarding certificate exchange.

A practical example of how I use EJBCA Enterprise daily is to deliver certificates for the appropriate client, ensuring EJBCA provides all requested certificates and can publish information about revoked certificates through the CRL. There is a law in our country that requires us to issue certificates for user authentication with a certificate lifetime of two years. I use EJBCA Enterprise for this, modifying and adjusting all certificate configurations, and I can also enforce certificate requests. For instance, if a requested certificate is produced with a public key having a weak exponent, we cannot accept it. This involves configuring and ensuring the solution works properly.

Regarding my main use case and daily tasks with EJBCA Enterprise, I can confirm that it is very flexible, allowing us to accomplish what we need. It is a very good PKI solution that enables us to generate certificates and ensure they comply with specific regulations or client needs. The daily tasks revolve around this flexibility, and EJBCA Enterprise excels in that area. I would also mention that communication with the support portal about Keyfactor is decent for regular questions, but when seeking expertise on the solution, it can be challenging.

EJBCA Enterprise has positively impacted my organization by providing flexibility regarding certificate profiles. Previously, I utilized another PKI solution from a well-regarded vendor, but EJBCA Enterprise allows me to create certificates as needed, filter requests efficiently, and implement mechanisms quickly while adhering to regulatory duties concerning certificates. EJBCA Enterprise offers precision in certificate management.

The best feature EJBCA Enterprise offers is its support, which provides good answers to questions. Additionally, it provides a very complete registration authority within the solution, supplying all necessary information about certificates, including trust chains and CRLs. It also provides numerous logs and many possibilities regarding certificate requests without a registration authority, such as ACME and SCEP, which can be beneficial in some environments. An important capability is the ability to build a custom PKI with multiple HSMs, which is a major advantage since EJBCA Enterprise can integrate with various HSMs from different vendors. A notable feature is the extensive configuration possibilities regarding certificate templates and profiles, offering unparalleled flexibility compared to other PKI solutions on the market. While the user experience may be slightly complex, I can essentially customize certificates in various formats, such as X.509, SSH, or ITSM format, making it a very comprehensive PKI solution.

EJBCA Enterprise needs to improve its user experience regarding the UI.

EJBCA Enterprise could be improved by simplifying the deployment process. Currently, making a custom installation requires creating and deploying WildFly before the EJBCA Enterprise installation, which adds complexity. Additionally, I believe EJBCA Enterprise should enhance its REST API options, as the current offerings are limited compared to the very complete SOAP API. Furthermore, deploying an OCSP server could improve the certificate situation by providing real-time updates on certificate status for users who may not be well-versed in cryptography. Lastly, EJBCA Enterprise should develop better data exposure so that if a team wants real-time data access in the PKI about certificates, there would be an endpoint for that, allowing for statistical insights.

I have been using EJBCA Enterprise for two years.

EJBCA Enterprise is very stable.

EJBCA Enterprise is very scalable. As long as your infrastructure permits, you can add and request as many certificates as you want. The only limitation is the infrastructure itself.

Customer support is good for regular questions, but when I require expert advice on high-skill questions, it can be challenging. I would rate customer support a six on a scale of one to ten.

My advice for others looking into using EJBCA Enterprise is to have a solid understanding of PKI and RFC recommendations before beginning, as EJBCA Enterprise offers many possibilities that can be overwhelming. Knowing what you want beforehand allows you to effectively build what you need using EJBCA Enterprise.

My main use case for EJBCA Enterprise is for certificate issuance for users and in the digital signature company.

A specific example of how I use EJBCA Enterprise for certificate issuance and digital signatures in my company is that digital signatures are used in my regions for signing PDF documents in business-to-customer business models, and our regulatory compliance is aligned with the Ministry of Information and Digital as a root CA in Indonesian regions.

EJBCA Enterprise is only used for digital signatures in my company and for generating TLS or SSL certificates for internal users.

EJBCA Enterprise has positively impacted our organization. However, we still struggle with regulatory compliance. EJBCA Enterprise is not used or approved for public use at this time, as we currently only use it internally until we receive permission to make the product public, allowing customers to use our applications with EJBCA Enterprise as the certificate tool for issuance.

Internally, EJBCA Enterprise helps my team with multi-factor authentication for accessing EJBCA Enterprise as our core system. We can install certificates for super administrators, so not all internal staff can use EJBCA Enterprise—only designated personnel.

The best features EJBCA Enterprise offers are that it is very easy to install, especially with the appliance or OVA version we are using. It integrates easily with HSM, it is easy to monitor because it has a good GUI and website interface, and it is more secure than other competitors.

The features that help my team day-to-day, such as easy integration with HSM and having a good GUI, allow us to simply deploy EJBCA Enterprise into virtual machines. The appliance website provides options to integrate with HSM by simply inputting the IP and port to test the connections, ensuring all integrations are successfully connected.

The new version of EJBCA Enterprise allows us to back up the system and logs more easily, providing a restore menu in the appliance web interface.

EJBCA Enterprise can be improved once we start the digital signature business and after our business makes a decision to use EJBCA Enterprise at scale.

I chose a rating of seven based on my seven years of experience. I assigned a three rating because EJBCA Enterprise is a high-resource system, and there are instances where the CPU peaks for no apparent reason, making it difficult to investigate.

I have been using EJBCA Enterprise for almost seven years.

We have encountered sudden issues within our company related to our core systems regarding EJBCA Enterprise's scalability.

EJBCA Enterprise provides access to their support, which is very helpful.

EJBCA Enterprise's customer support always responds to our issues when we submit tickets from the Keyfactor principal portals.

I rate the customer support a six.

From the beginning, we made a decision to start using EJBCA Enterprise in our company.

EJBCA Enterprise is our core system. The employees needed are not for using EJBCA Enterprise but for serving our public users.

My experience with pricing shows that it is very high and expensive. The setup cost is manageable, but licensing is expensive each year.

On a scale of one to ten, I rate EJBCA Enterprise a seven.

Regarding EJBCA Enterprise's AI capabilities, I recommend its governance and security features, as they provide very high security through multi-factor authentication, login via certificates, and options for access control for those who can use EJBCA Enterprise.

My advice to others considering EJBCA Enterprise is that I recommend using the new version with the OVA version, especially the appliance for on-premises deployment, as it is very easy to install, integrate, and work with APIs, along with other components such as EJBCA Enterprise as a certificate authority or EJBCA Enterprise as a validation authority, including other products from Keyfactor such as SignServer and HSM.