Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1529262

Summary: OVN provider password added by engine-setup must be encrypted
Product: [oVirt] ovirt-engine Reporter: Marcin Mirecki <mmirecki>
Component: Setup.EngineAssignee: Marcin Mirecki <mmirecki>
Status: CLOSED CURRENTRELEASE QA Contact: Mor <mkalfon>
Severity: medium Docs Contact:
Priority: high    
Version: 4.2.1CC: bugs, danken, mkalfon, mmirecki
Target Milestone: ovirt-4.2.1Flags: rule-engine: ovirt-4.2+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
The password will be encrypted whenever it will be saved to the db again. To save , it is enough to open the provider dialog, edit the provider and click ok.
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 11:54:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marcin Mirecki 2017-12-27 11:13:22 UTC
Password added to the provider table is not encrypted.

Comment 1 Mor 2018-01-08 08:16:37 UTC
Is it possible to also handle upgrade scenarios (where it is not already encrypted)?

Comment 2 Mor 2018-01-08 14:09:09 UTC
Verified on:
RHV 4.2.1-0.2.el7
ovirt-engine-4.2.1-0.2.el7.noarch
ovirt-provider-ovn-1.2.3-1.el7ev.noarch

Engine db --> providers --> auth_password fields are not clear-text.

Comment 3 Marcin Mirecki 2018-01-24 10:31:39 UTC
The password will be encrypted whenever it will be saved to the db again.
To save , it is enough to open the provider dialog, edit the provider and click ok.

Comment 4 Sandro Bonazzola 2018-02-12 11:54:48 UTC
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.