-
Notifications
You must be signed in to change notification settings - Fork 599
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
CORE-3168 support p12 #21313
CORE-3168 support p12 #21313
Conversation
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/51285#01909987-db34-4048-ad16-d61e783972e3 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/51285#01909988-4371-4f37-b903-68ef89793006 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/51285#01909988-4374-4260-96b8-e4a8fa10be48 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. several comments, all nitpicks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This adds support for P12 password files, and also seems to extend the implementation to accept multiple key/cert file pairs instead of just a single pair. The test coverage looks good and I don't see any controversial points.
bc8be0f
to
4818ef6
Compare
Force push
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll trust Oren and Ben to approve the changes they requested earlier.
12ea872
4818ef6
to
12ea872
Compare
Force push
|
PKCS#12 files (or PFX files) can be used to hold various cryptographic keys and certificates in a secure way. These files are encrypted using a user provided password and allows for secure transmission of keys and certs from an issuer to an endpoint. This commit allows for users of Redpanda to use a P12 file (with a supplied password for decryption) instead of a plain-text key and cert when setting up TLS configurations. Signed-off-by: Michael Boquard <michael@redpanda.com>
Signed-off-by: Michael Boquard <michael@redpanda.com>
Signed-off-by: Michael Boquard <michael@redpanda.com>
Signed-off-by: Michael Boquard <michael@redpanda.com>
Signed-off-by: Michael Boquard <michael@redpanda.com>
Added PKCS#12 file smoke test Signed-off-by: Michael Boquard <michael@redpanda.com>
12ea872
to
90d4bdb
Compare
Force push
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Hi @michael-redpanda what do we need to review for docs? I don't see any user-facing strings. |
There are 2 new configs AIUI. cc @deniscoady who can help with docs |
@Deflaimun I filed a docs issue (https://redpandadata.atlassian.net/browse/DOC-539) for this new feature, so it's more of an FYI |
} | ||
|
||
return std::nullopt; | ||
} | ||
|
||
std::ostream& operator<<(std::ostream& o, const config::p12_container& p) { | ||
fmt::print(o, "{{ p12 file: {}, p12 password: REDACTED }}", p.p12_password); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@michael-redpanda did you intend to print the file, rather than the password?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
presumably, yeah, but Mike can confirm. PR because it's a trivial: #23249
Adds support for using PKCS#12 files in our TLS node config.
Backports Required
Release Notes
Features