Updated openstack/openstack
Project: openstack/keystone  8c08998b616b66203adb9f1cd95897a61b2b5a1d
null
Properly handle unicode & utf-8 in LDAP

This patch adds all the necessary type conversions between the LDAP
API's.

* string literals are unicode

* unicode strings are utf-8 encoded before calling LDAP

* utf-8 strings received from the LDAP API are decoded into unicode

* string classes use the six.text_type for Python 2 vs. Python 3
  compatibility

* the fake LDAP implementation was reworked such that it's external
  API only handles UTF-8 encoded strings but only uses unicode
  internally. This is because internally it must be able to operate on
  logical characters in order to perform string operations on it's
  data. This is very much akin to what happens in a real LDAP
  implementation, the interface is UTF-8 but operations occur on
  decoded logical characters.

Unicode tests that were skipped are now re-enabled.

Partial-Bug: 1172106
Change-Id: Icce6b508f748214e241de40c3c9389b2caccea83
Updated openstack/openstack
Project: openstack/keystone  03c146cd0693fed58c1d96b7afaf076bb98d7e1e
null
Expand the use of non-ascii values in ldap test

Very few of the ldap tests were using non-ascii values, in fact
non-ascii values were restricted to only specific tests that
had 'unicode' in their test name. This is very weak test coverage.

This patch replaces all occurances of 'fake1', the standard string
used in the tests for test value with 'fäké1' where the a has an
umlaut and the e has a diacritical. Visually they look almost the
same but will trigger the type of encoding exceptions we've seen
in the past.

Closes-Bug: 1172106

Change-Id: I03b10f3da93a8fb388baacb00532c03019f327c0
Updated openstack/openstack
Project: openstack/python-keystoneclient  5d6137f26c3e9ba65e47476232ec0af632086e16
null
Remove releases.rst from keystone docs

The most recent update to releases.rst was made back in 2012,
but it's references in the docs page. It is providing false
(or at least, inaccurate) information. Suggest removing it
since the server side doesn't have a release related file either.

Change-Id: If2a71b55117c450afdade3cad697eba5a626263f
Updated openstack/openstack
Project: openstack/keystone  c3f244b3bdde6cfa24ea605b83ea184d7f8fac3d
null
Check domain_id with equality in assignment kvs

It was noticed in https://review.openstack.org/70816 that the kvs
assignment backend was using a contains check instead of an equality
check which comparing domain_ids.

Change-Id: Ib1b51298c8171151844caaa5ab694117e68374e7