SPIFFE Overview Concepts Ecosystem Community Presentations Get Involved
Standards
SPIFFE SPIFFE ID and Verifiable Identity Document SPIFFE Trust Domain and Bundle JWT-SVID X509-SVID WIT-SVID SPIFFE Workload API SPIFFE Workload Endpoint SPIFFE Broker API SPIFFE Broker Endpoint SPIFFE Federation Specification Stability
SPIRE
About
Concepts Use Cases Comparisons Case Studies
Try
Quickstart for Linux and MacOS X Quickstart for Kubernetes Quickstart for Docker
Plan
Scaling SPIRE Extending
Deploy
Getting SPIRE Install Server Install Agent Configuring Registering workloads Working with SVIDs SPIFFE Library Usage Examples SPIRE Agent Configuration Reference SPIRE Server Configuration Reference SPIRE Telemetry Configuration
Maintain
Upgrade/Downgrade SPIRE
Helm Charts Hardened
About
Installation Upgrading Service Selection Recommendations Exposing Services Identifiers Namespaces
Advanced
Nested SPIRE Federation Local Mirrors
Integrate SPIRE
Securing Microservices
Using Envoy with SPIRE SPIRE with Envoy and X.509-SVIDs SPIRE with Envoy and JWT-SVIDs Spire with OPA + Envoy + X.509-SVIDs Spire with OPA + Envoy + JWT-SVIDs
SVID Authentication
AWS OIDC Authentication Vault Integration Example
SPIRE Architecture
Nested SPIRE Example SPIRE Federation Example
v1.15.1 Latest

Get Involved

How to navigate and connect with the SPIFFE community

SPIFFE is guided by a small but very active community of passionate software engineers with empathy for the problems that the project is tackling.

Join the Community

  • Slack — Most real-time discussions happen on SPIFFE’s Slack channels at https://spiffe.slack.com. You can join here.

  • Mailing lists — Announcements occur in the SPIFFE Google Group. There is also a users and developers list.

  • Special Interest Groups and Working Groups — The broader SPIFFE community is self-organized into Special Interest Groups (SIGs) that coordinate to manage specific aspects of SPIFFE’s design, and Working Groups (WGs) that focus on short-term cross-SIG initiatives. A list of active SIGs and WGs can be found here.

  • Social media — Follow us on Twitter.

Contribute to the Project

You can contribute to SPIFFE and SPIRE by filing issues and submitting pull requests on GitHub. See these contribution guidelines for details such as GitHub etiquette and coding conventions:

While anyone is welcome to propose contributions via pull requests, we strongly encourage significant contributions - particularly those that might require a significant change to core components - to be first discussed and a high level design agreed upon with the appropriate SIGs or WGs (see above).

Day to day contributions are vetted by the project’s maintainers. Overall project direction, guidance and conflict resolution is overseen by the projects’ Technical Steering Committee. Full details on this process can be found in the project GOVERNANCE page.

Add SPIFFE Support to Other Projects

Contributions don’t have to land in the SPIFFE and SPIRE repositories to move the project forward. Adding SPIFFE support to other tools, libraries, and platforms is one of the most valuable ways to grow the SPIFFE ecosystem. Some good starting points:

  • Consume SPIFFE identities in your application or library — add support for fetching identities from the SPIFFE Workload API, for example by building on one of the SDKs listed on the ecosystem page.

  • Accept SVIDs in a tool you maintain or use — allow workloads to authenticate to a database, proxy, message broker, or other service with an X.509-SVID or JWT-SVID instead of a shared secret.

  • List a project on the ecosystem page — if a project already supports SPIFFE but isn’t listed, add an entry to data/ecosystem.yaml and open a pull request against spiffe/spiffe.io.

If you’re unsure where to start, ask in the SPIFFE Slack channels or bring your idea to one of the SIGs or WGs listed above — the community is happy to help scope out an integration.

SPIFFE and SPIRE Branding Media Library

Find SPIFFE and SPIRE logos here: