Bug 782806
Summary: | [RFE] Python qpid client ssl support | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Frantisek Reznicek <freznice> |
Component: | python-qpid | Assignee: | Rafael H. Schloming <rafaels> |
Status: | CLOSED ERRATA | QA Contact: | Petr Matousek <pematous> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | Development | CC: | esammons, iboverma, jross, lzhaldyb, matt, mcressma, mgoulish, pematous, pmoravec, tross |
Target Milestone: | 2.3 | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | python-qpid-0.18-1 | Doc Type: | Enhancement |
Doc Text: |
Feature: SSL/TLS support for the messaging API. This allows clients using the messaging API to connect to the broker over a connection encrypted using SSL/TLS.
Reason: Previously users of the messaging API could only connect to the broker with unencrypted connections.
Result (if any):
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-03-06 18:54:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 850517, 885190, 895602 | ||
Bug Blocks: | 729391 |
Description
Frantisek Reznicek
2012-01-18 15:01:55 UTC
QPID-3175, destined for 0.16 *** Bug 729868 has been marked as a duplicate of this bug. *** *** Bug 694762 has been marked as a duplicate of this bug. *** The SSL/TLS is now supported by the messaging python API and the documentation is available. Tested on rhel5.{8,9} and rhel6.{3,4} (both x86_64, i386) Packages used for testing: python-qpid-0.18-4 qpid-cpp-*-0.18-14 qpid-qmf-0.18-15 qpid-tools-0.18-8 -> VERIFIED Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0561.html |