spire icon indicating copy to clipboard operation
spire copied to clipboard

The SPIFFE Runtime Environment

Results 473 spire issues
Sort by recently updated
recently updated
newest added

Agents used to issue JWT-SVIDs with a TTL hardcoded to 5 minutes. When we refactored the Server APIs, the agents were changed to consume the new Server APIs. The NewJWTSVID...

priority/backlog

Consider the following sequence of events: 1. A SPIRE Agent is initialized and successfully attests to SPIRE Server 2. While the Agent has a valid Agent SVID still cached on...

priority/backlog

#3130 describes adding code to clean up orphaned entry-related rows caused by bugs that were fixed as of 1.3.1. With our upgrade path, we can assume that existing deployments will...

priority/urgent

When the notifier interface was introduced, the intention was to fill a handful of use cases we had around arbitrary event-driven actions. Updating the bundle in a remote location any...

priority/backlog

Data in the `attested_node_entries` and `node_resolver_map_entries` tables is left in the database indefinitely. There are cases when this data may no longer be valuable to retain, such as when the...

help wanted
priority/backlog

This is a follow-up on #2342. * **Version**: 1.3.0 * **Platform**: Windows 10 20H2 * **Subsystem**: spire-server I sadly missed out on the switch to named pipes a month ago....

priority/backlog

* **Version**: 1.2.1 * **Platform**: apline 3.15 (x86_64) * **Subsystem**: build The go-check hook doesn't appear to be working as intended when run in an Alpine build container. ``` Step...

priority/backlog

The result of CI/CD process should be a multi-arch image consumable by both ARM64 and x86 arch.

help wanted
priority/backlog

The SPIFFE bundle specification allows for an optional sequence number to be set, which allows consumers to understand which bundles are "newer" or "older", and also allows them to measure...

priority/backlog

### Summary This ticket is intended to: (1) be informational, and (2) track an underlying issue that results from use of the `unix` workload attestor with `discover_workload_path` enabled. ### Description...

priority/backlog