Skip to content

Issues: bloomberg/vault-auth-spire

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6 Open 2 Closed
6 Open 2 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Ownership of X509-SVIDs are currently unknown discussion Issues requiring community discussion release-blocker Until resolved no new releases should be cut
#12 opened Nov 7, 2019 by dennisgove
2
SvidVerifier::Verify assumes an x509-based SVID release-blocker Until resolved no new releases should be cut
#8 opened Oct 28, 2019 by dennisgove
Add Integration Tests release-blocker Until resolved no new releases should be cut
#5 opened Oct 25, 2019 by dennisgove
1
Add Unit Tests release-blocker Until resolved no new releases should be cut
#4 opened Oct 25, 2019 by dennisgove
1
@pawalt
Support Spire as a TrustSource
#2 opened Oct 25, 2019 by dennisgove
1
@pawalt
2
Discussion: Convert SPIFFE ID into a list of Vault policy IDs discussion Issues requiring community discussion help wanted Extra attention is needed release-blocker Until resolved no new releases should be cut
#1 opened Oct 25, 2019 by dennisgove
ProTip! Exclude everything labeled bug with -label:bug.