keystone user-update with ldap not working

Bug #1069667 reported by Andre Naehring
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
Fix Released
Medium
Unassigned

Bug Description

Using ldap as backend for keystone it is possible to add users, but updating them is not possible.

First example, driver is "driver = keystone.identity.backends.sql.Identity":

oscontroller:/etc/keystone # keystone user-update --enabled=false 336ad698c2e2457bb980f5b113dba7ef
User has been updated.

This is using LDAP ( "keystone.identity.backends.ldap.Identity"):

# keystone user-update --enabled=true a31ae867e31d444e8ef517f5a1a98012
No handlers could be found for logger "keystoneclient.client"
Unable to update user: An unexpected error prevented the server from fulfilling your request. 'name' (HTTP 500)

Revision history for this message
Jose Castro Leon (jose-castro-leon) wrote :

There is no mapping yet to the property enabled in ldap. Maybe this is the reason that it does not work

Revision history for this message
Joseph Heck (heckj) wrote :

If the back-end doesn't implement the relevant feature (i.e. modifing the enabled field in this case), then the service should at least return a 501 NotImplemented or 505 NotSupported rather than a generic 500 error.

Changed in keystone:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Jose Castro Leon (jose-castro-leon) wrote :

In the latest update, I have included the enabled field capability could you please recheck?
There is some documentation to read because not all LDAP servers handle that field with the same way (specially AD)

Revision history for this message
Brant Knudson (blk-u) wrote :
Revision history for this message
Dolph Mathews (dolph) wrote :

I believe this was fixed by the above.

Changed in keystone:
milestone: none → grizzly-3
status: Triaged → Fix Committed
Thierry Carrez (ttx)
Changed in keystone:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in keystone:
milestone: grizzly-3 → 2013.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.