Skip to content
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.

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

SvidVerifier::Verify assumes an x509-based SVID #8

Open
dennisgove opened this issue Oct 28, 2019 · 0 comments
Open

SvidVerifier::Verify assumes an x509-based SVID #8

dennisgove opened this issue Oct 28, 2019 · 0 comments
Labels
release-blocker Until resolved no new releases should be cut

Comments

@dennisgove
Copy link
Contributor

The current implementation of SvidVerifier::Verify assumes the SVID will be an x509-SVID and doesn't consider the possibility of a JWT-SVID.

Purpose: This issue will track the discussion and implementation of one of the following

  1. Implementation of support for JWT-SVID documents
  2. Creation of clear documentation describing support for only x509-SVID documents
@dennisgove dennisgove added the release-blocker Until resolved no new releases should be cut label Oct 28, 2019
@dennisgove dennisgove changed the title SvidVerifier::Verify assumes an x509-based SVID SvidVerifier::Verify assumes an x509-based SVID Oct 28, 2019
dennisgove added a commit to dennisgove/vault-auth-spire that referenced this issue Oct 31, 2019
…ments

Currently the plugin only supports (and expects) X509-SVID documents as described in issue bloomberg#8. The README has been updated to reflect that current limitation.
dennisgove added a commit to dennisgove/vault-auth-spire that referenced this issue Oct 31, 2019
…ments

Currently the plugin only supports (and expects) X509-SVID documents as described in issue bloomberg#8. The README has been updated to reflect that current limitation.

Signed-off-by: Dennis Gove <[email protected]>
dennisgove added a commit that referenced this issue Nov 1, 2019
…ments

Currently the plugin only supports (and expects) X509-SVID documents as described in issue #8. The README has been updated to reflect that current limitation.

Signed-off-by: Dennis Gove <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blocker Until resolved no new releases should be cut
Projects
None yet
Development

No branches or pull requests

1 participant