Bug 1042948

Summary: [RFE][oslo]: Use keyring for all config based passwords/users
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/oslo/+spec/pw-keyrings
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_approved
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:14:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description RHOS Integration 2013-12-13 16:45:59 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/oslo/+spec/pw-keyrings.

Description:

Instead of having config files with passwords/users in them (which is bad) there should be some integration with the standard keyring providers in various operating systems, this python project @ http://pypi.python.org/pypi/keyring seems to provide some of this. It seems like openstack common should provide a little helper class to allow config to use that, for sections of config that need to be "secure", ie for a start, users and passwords should not be in clear-text (at least the passwords for stage 0).

Specification URL (additional information):

None