Skip to content

Comments

[pulsar-client] support jks truststore with pem key/certchain files for tls auth#10909

Closed
rdhabalia wants to merge 1 commit intoapache:masterfrom
rdhabalia:tls_jks2
Closed

[pulsar-client] support jks truststore with pem key/certchain files for tls auth#10909
rdhabalia wants to merge 1 commit intoapache:masterfrom
rdhabalia:tls_jks2

Conversation

@rdhabalia
Copy link
Contributor

Motivation

Right now, Pulsar client supports keystore if user has key/cert and trust store in jks format. However, if user is having key/cert in pem format and turst-store in jks format then user can't use it in current pulsar-client implementation. So, add support to use key/cert with pem format along with trust-store in jks format. It helps user to skip extra management of turst-cert format conversion.

@rdhabalia rdhabalia added this to the 2.9.0 milestone Jun 12, 2021
@rdhabalia rdhabalia self-assigned this Jun 12, 2021
@eolivelli eolivelli modified the milestones: 2.9.0, 2.10.0 Oct 6, 2021
@codelipenghui codelipenghui modified the milestones: 2.10.0, 2.11.0 Jan 18, 2022
@codelipenghui
Copy link
Contributor

The pr had no activity for 30 days, mark with Stale label.

@github-actions
Copy link

github-actions bot commented Mar 4, 2022

@rdhabalia:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

@tisonkun
Copy link
Member

tisonkun commented Dec 9, 2022

Closed as stale and conflict. Please rebase and resubmit the patch if it's still relevant.

@tisonkun tisonkun closed this Dec 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants