Bug 1444893 - [RFE] OVN provider TLS encryption support for authentication and clients traffic
Summary: [RFE] OVN provider TLS encryption support for authentication and clients traffic
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-provider-ovn
Classification: oVirt
Component: provider
Version: 1.0.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.2.0
: ---
Assignee: Marcin Mirecki
QA Contact: Mor
URL:
Whiteboard:
Depends On:
Blocks: 1445172
TreeView+ depends on / blocked
 
Reported: 2017-04-24 13:46 UTC by Mor
Modified: 2019-04-28 13:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2017-12-20 11:28:59 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+
gklein: testing_plan_complete-
ylavi: planning_ack+
danken: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 77807 0 master MERGED packaging: re-enable SSL support for OVN northdb connection 2017-07-31 09:33:48 UTC

Description Mor 2017-04-24 13:46:57 UTC 
Description of RFE:

1. OVN provider should support SSL to authenticate provider user requests. Currently in RHV, we use unencrypted HTTP protocol to communicate with the provider.

2. OVN traffic between OVN hosts (controllers) and OVN-central server (OVSDB) should be encrypted using SSL. In 2.7.1 http://openvswitch.org/releases/NEWS-2.7.0 version it is being supported officially by the OVN project.

Additional info:

External BZ opened by Marcin Mirecki: 
https://bugzilla.redhat.com/show_bug.cgi?id=1396143 for OVS/OVN team.
Comment 1 Mor 2017-09-03 08:56:10 UTC 
Verified on: 
4.2.0-0.0.master.20170901193740.git7900511.el7.centos

NB-DB and SB-DB are configured by default for SSL.
Comment 2 Sandro Bonazzola 2017-12-20 11:28:59 UTC 
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.