Reviewed: https://review.openstack.org/5162 Committed: http://github.com/openstack/keystone/commit/6f2c858f4382395bd4b4232e7ba3dd509327e4c6 Submitter: Jenkins Branch: master
commit 6f2c858f4382395bd4b4232e7ba3dd509327e4c6 Author: Brian Lamar <email address hidden> Date: Fri Mar 9 15:24:25 2012 -0500
Update get_metadata to return {}
Fixes bug 951093
While the actual issue was encountered in keystone/service.py, the underlying issue is that all identity backends seems to be returning None when no metadata is found for a user. I would argue that returning {} makes it easier on clients.
Change-Id: I06faf755cc0dbe45b5d0a0f86c6235b27c856047
Reviewed: https:/ /review. openstack. org/5162 github. com/openstack/ keystone/ commit/ 6f2c858f4382395 bd4b4232e7ba3dd 509327e4c6
Committed: http://
Submitter: Jenkins
Branch: master
commit 6f2c858f4382395 bd4b4232e7ba3dd 509327e4c6
Author: Brian Lamar <email address hidden>
Date: Fri Mar 9 15:24:25 2012 -0500
Update get_metadata to return {}
Fixes bug 951093
While the actual issue was encountered in keystone/ service. py,
the underlying issue is that all identity backends seems to be
returning None when no metadata is found for a user. I would argue
that returning {} makes it easier on clients.
Change-Id: I06faf755cc0dbe 45b5d0a0f86c623 5b27c856047