keystoneclient password plugin reports "user-name" as parameter but only usern

Bug #1423660 reported by Haneef Ali on 2015-02-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fernando Diaz

Bug Description

Keystone client pluggin reports the parameter name as "user-name". But only "username" works from keystonemiddleware. Note: there is no "-"

My working config

identity_uri = http://localhost:35357/
auth_section = generic_password

auth_plugin = password
#user_name = nova
username = nova
user_domain_id = default
project_name = service
project_domain_id = default
password = DontTellAnyOne
auth_url =

//stevedore output
 auth-url: Authentication URL
 auth-url: Authentication URL
 domain-id: Domain ID to scope to
 domain-name: Domain name to scope to
 tenant-id: Tenant ID to scope to
 tenant-name: Tenant name to scope to
 project-id: Project ID to scope to
 project-name: Project name to scope to
 project-domain-id: Domain ID containing project
 project-domain-name: Domain name containing project
 trust-id: Trust ID
 user-name: Username
 user-domain-id: User's domain id
 user-domain-name: User's domain name
 password: User's password

Haneef Ali (haneef) wrote :

If I use "user_name" , I get an error saying I need either "name" or "id" for user. If I use "username" , it works. I don't have any other settings other than the one I posted above

Fernando Diaz (diazjf) on 2015-10-21
Changed in python-keystoneclient:
assignee: nobody → Fernando Diaz (diazjf)
Fernando Diaz (diazjf) wrote :

Hey Haneef,

Can you give me more info on your setup and what I can do to recreate the error?

Seems as though "user-name" has been deprecated as an option in the python-client:

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers