Bug 1041450 - [RFE][nova]: vmware driver support for VMware SSO
Summary: [RFE][nova]: vmware driver support for VMware SSO
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 16:09 UTC by RHOS Integration
Modified: 2015-03-19 17:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:23:02 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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