Bug 1041450

Summary:	[RFE][nova]: vmware driver support for VMware SSO
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, sgordon, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/nova/+spec/vmware-sso-support
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_drafting
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:23:02 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-12 16:09:42 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/vmware-sso-support.

Description:

The current driver stores usernames and passwords in plain text. The VMware vSphere and vCenter products have their own SSO system. At the driver level, we should allow a customer to optionally configure the SSO keys and tokens so that they do not have to store the password in plain text on their nova-compute node.

Areas to consider:
* keystone integration with AD plus vCenter integration with AD may solve some user related issues
* keystone integration with vCenter SSO?
* vCenter SSO integration with Keystone?
* can we use long running HoK tokens or other non-password based tokens for authentication?

This may be important to implementing the feature:
https://wiki.openstack.org/wiki/Keystone/Federation/Blueprint#Mode_of_Operation_with_Holder_of_Key_Verification


Specification URL (additional information):

None