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.

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

Jump to bottom

Adding SSL support into kafka-python #447

Closed
Ormod opened this issue Aug 25, 2015 · 1 comment
Closed

Adding SSL support into kafka-python #447

Ormod opened this issue Aug 25, 2015 · 1 comment

Comments

@Ormod
Copy link
Contributor

Ormod commented Aug 25, 2015

Now that Kafka-1690 (https://issues.apache.org/jira/browse/KAFKA-1690) has been merged into Kafka master it would be great if python-kafka could use TLS as well.
@Ormod Ormod changed the title Adding SSL support into the kafka-python Adding SSL support into kafka-python Aug 25, 2015
Ormod added a commit to Ormod/kafka-python that referenced this issue Nov 9, 2015
@Ormod
ssl: Support using client-side SSL certificates, closes dpkp#253 and d…
3225767 
…pkp#447

Kafka 0.9.0+ supports using SSL encrypted connections authenticated
with client certificates. This adds support for these. After this
when using SSL/TLS for Kafka broker connections,
TLSv1.0+ is used for authentication, protocols earlier than that are
deprecated from the get go as insecure.

If keyfile/certificate are left empty, the client can still use
SSL/TLS for the transport, but in that case the server must be
configured to accept unauthenticated users.
Ormod added a commit to Ormod/kafka-python that referenced this issue Nov 9, 2015
@Ormod
ssl: Support using client-side SSL certificates, closes dpkp#253 and d…
4d358f7 
…pkp#447

Kafka 0.9.0+ supports using SSL encrypted connections authenticated
with client certificates. This adds support for these. After this
when using SSL/TLS for Kafka broker connections,
TLSv1.0+ is used for authentication, protocols earlier than that are
deprecated from the get go as insecure.

If keyfile/certificate are left empty, the client can still use
SSL/TLS for the transport, but in that case the server must be
configured to accept unauthenticated users.
Ormod added a commit to Ormod/kafka-python that referenced this issue Nov 16, 2015
@Ormod
ssl: Support using client-side SSL certificates, closes dpkp#253 and d…
78336ea 
…pkp#447

Kafka 0.9.0+ supports using SSL encrypted connections authenticated
with client certificates. This adds support for these. After this
when using SSL/TLS for Kafka broker connections,
TLSv1.0+ is used for authentication, protocols earlier than that are
deprecated from the get go as insecure.

If keyfile/certificate are left empty, the client can still use
SSL/TLS for the transport, but in that case the server must be
configured to accept unauthenticated users.
Ormod added a commit to Ormod/kafka-python that referenced this issue Nov 16, 2015
@Ormod
ssl: Support using client-side SSL certificates, closes dpkp#253 and d…
fa2c0fc 
…pkp#447

Kafka 0.9.0+ supports using SSL encrypted connections authenticated
with client certificates. This adds support for these. After this
when using SSL/TLS for Kafka broker connections,
TLSv1.0+ is used for authentication, protocols earlier than that are
deprecated from the get go as insecure.

If keyfile/certificate are left empty, the client can still use
SSL/TLS for the transport, but in that case the server must be
configured to accept unauthenticated users.
saaros added a commit to aiven/kafka-python that referenced this issue Nov 17, 2015
@saaros
Merge pull request #4 from Ormod/ssl
2b5200c 
ssl: Support using client-side SSL certificates, closes dpkp#253 and dpkp#447
Ormod added a commit to Ormod/kafka-python that referenced this issue Nov 18, 2015
@Ormod
ssl: Support using client-side SSL certificates, closes dpkp#253 and d…
45a0510 
…pkp#447

Kafka 0.9.0+ supports using SSL encrypted connections authenticated
with client certificates. This adds support for these. After this
when using SSL/TLS for Kafka broker connections,
TLSv1.0+ is used for authentication, protocols earlier than that are
deprecated from the get go as insecure.

If keyfile/certificate are left empty, the client can still use
SSL/TLS for the transport, but in that case the server must be
configured to accept unauthenticated users.
@dpkp
Copy link
Owner

dpkp commented Jan 27, 2016

dup of #253

@dpkp dpkp closed this as completed Jan 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Ormod @dpkp