Skip to content

Keyfactor/ejbca-spire-upstreamauthority-plugin

EJBCA UpstreamAuthority plugin for SPIRE Server

EJBCA UpstreamAuthority plugin for SPIFFE SPIRE using the SPIRE Plugin SDK

Integration status: Production - Ready for use in production environments.

About the Keyfactor API Client

This API client allows for programmatic management of Keyfactor resources.

Support for EJBCA UpstreamAuthority plugin for SPIRE Server

EJBCA UpstreamAuthority plugin for SPIRE Server is open source and supported on best effort level for this tool/library/client. This means customers can report Bugs, Feature Requests, Documentation amendment or questions as well as requests for customer information required for setup that needs Keyfactor access to obtain. Such requests do not follow normal SLA commitments for response or resolution. If you have a support issue, please open a support ticket via the Keyfactor Support Portal at https://support.keyfactor.com/

To report a problem or suggest a new feature, use the Issues tab. If you want to contribute actual bug fixes or proposed enhancements, use the Pull requests tab.


EJBCA UpstreamAuthority plugin for SPIRE Server

Integration Status: production Release Issues GitHub Downloads (all assets, all releases)

Support · License · Related Integrations

Support

The EJBCA UpstreamAuthority plugin for SPIRE Server is open source and there is no SLA. Keyfactor will address issues as resources become available. Keyfactor customers may request escalation by opening up a support ticket through their Keyfactor representative.

To report a problem or suggest a new feature, use the Issues tab. If you want to contribute actual bug fixes or proposed enhancements, use the Pull requests tab.

EJBCA UpstreamAuthority plugin for SPIRE Server

EJBCA logo EJBCA logo

Go Report Card

The ejbca UpstreamAuthority plugin uses a connected EJBCA to issue intermediate signing certificates for the SPIRE server. The plugin can authenticate to EJBCA using mTLS (client certificate) or using the OAuth 2.0 "client credentials" token flow (sometimes called two-legged OAuth 2.0).

System Requirements

To build

To use

  • EJBCA Community or EJBCA Enterprise
    • The "REST Certificate Management" protocol must be enabled under System Configuration > Protocol Configuration.

Getting Started

Community Support

In the Keyfactor Community, we welcome contributions.

The Community software is open-source and community-supported, meaning that no SLA is applicable.

Commercial Support

Commercial support is available for EJBCA Enterprise.

License

For License information, see LICENSE.

Related Projects

See all Keyfactor EJBCA GitHub projects.

License

Apache License 2.0, see LICENSE.

Related Integrations

See all Keyfactor integrations.

About

EJBCA UpstreamAuthority plugin for SPIFFE SPIRE using the SPIRE Plugin SDK

Topics

Resources

License

Contributing

Security policy

Stars

Watchers

Forks

Packages

No packages published

Contributors 2

  •  
  •