Bug 1529262 - OVN provider password added by engine-setup must be encrypted
Summary: OVN provider password added by engine-setup must be encrypted
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Setup.Engine
Version: 4.2.1
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.2.1
: ---
Assignee: Marcin Mirecki
QA Contact: Mor
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-27 11:13 UTC by Marcin Mirecki
Modified: 2018-02-12 11:54 UTC (History)
4 users (show)

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.
Clone Of:
Environment:
Last Closed: 2018-02-12 11:54:48 UTC
oVirt Team: Network
Embargoed:
rule-engine: ovirt-4.2+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 85762 0 'None' MERGED packaging: encrypt ovn provider password before saving to db 2021-02-16 09:44:48 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.