Skip to content

Update plugin proto to send tls.ConnectionState (Op.2)#12581

Merged
ncabatoff merged 4 commits intohashicorp:mainfrom
tep:tls-state-plugins
Oct 7, 2021
Merged

Update plugin proto to send tls.ConnectionState (Op.2)#12581
ncabatoff merged 4 commits intohashicorp:mainfrom
tep:tls-state-plugins

Conversation

@tep
Copy link
Copy Markdown
Contributor

@tep tep commented Sep 19, 2021

This is a resubmission of #9240; it still fixes #9213

In order for external plugins to examine the client certificate(s)
presented during the original request into Vault, we need to marshal
that request's tls.ConnectionState across the gRPC boundary from the
Vault server to the external plugin process.

To that end, this change updates the protocol buffer (and associated
translation logic) used for communicating with external plugins to
include the logical.Connection's "ConnState" value -- thus making it
available to the logical.Request passed to callbacks defined by
external plugins.

@vercel vercel bot temporarily deployed to Preview – vault September 19, 2021 17:28 Inactive
@vercel vercel bot temporarily deployed to Preview – vault-storybook September 19, 2021 17:28 Inactive
@heatherezell
Copy link
Copy Markdown
Contributor

Hi @tep! It looks like there's some merge conflicts. Can you resolve those? Then, the tests all look good and we can do a deeper dive on the review.

@tep
Copy link
Copy Markdown
Contributor Author

tep commented Oct 7, 2021

@hsimon-hashicorp -- Conflicts resolved

@ncabatoff ncabatoff merged commit 7bd2be5 into hashicorp:main Oct 7, 2021
@ncabatoff
Copy link
Copy Markdown
Collaborator

Nice work, thanks @tep!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make TLS ConnectionState available to external plugins

3 participants