Bug 1041841

Summary: [RFE][python-keystoneclient]: Interoperability w/ Standard HTTP Authentication Mechanisms
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/python-keystoneclient/+spec/python-keystone-client-interroperate-http-auth-mechanisms
Whiteboard: upstream_milestone_none upstream_status_not-started upstream_definition_superseded
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:06:41 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 19:39:36 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/python-keystoneclient/+spec/python-keystone-client-interroperate-http-auth-mechanisms.

Description:

Keystone is moving towards being integrated into Apache as its strategic deployment model to gain all the benefits of being run as an Apache plugin.  One benefit from this would be able to take advantage of the standard HTTP authentication mechanisms that Apache supports.   To maximize the benefits obtained from this approach the python keystone client needs to add support for standard HTTP authentication mechanisms (e.g.  Kerberos, X509 Client cert, and basic-auth) from a client side perspective

Specification URL (additional information):

https://etherpad.openstack.org/python-keystone-client-interroperate-HTTP-Auth