Fix Jenkins translation jobs

The jobs keystone-propose-translation-update and
keystone-upstream-translation-update do not update from
transifex since our po files contain duplicate entries where obsolete
entries duplicate normal entries.

Remove all obsolete entries to fix the jobs.

NOTE: This is NOT a clean backport of the patch from master, but rather
this patch was generated similarly to the patch to master using
https://gist.github.com/dolph/9915293

Closes-Bug: #1299349

Change-Id: Ibbf26bb8158735a5dc57bff7d77a49e00239857c
Fix create_region_with_id raise 500 Error bug

1. add sql.handle_conflicts wrapper in sql backend driver.
2. check duplicate region id in kvs backend driver.
3. add 2 test cases to check exception.Conflict when create duplicate id region.

Closes-Bug: #1283904

Change-Id: Icfc5edf661501a5c134f324a76824812dbda2760
Sanitizes authentication methods received in requests.

When a user authenticates against Identity V3 API, he can specify
multiple authentication methods. This patch removes duplicates, which
could have been used to achieve DoS attacks.

Change-Id: Iec9a1875a4ff6e2fac0fb2c3db6f3ce34a5dfd1d
Closes-Bug: 1300274
Merge "Fix create_region_with_id raise 500 Error bug" into milestone-proposed
Sync from oslo db.sqlalchemy.migration

Sync the updated migration module to prevent errors on non-utf8
migrate_version and alembic_version tables (not controlled by the
schema migration directory).

Change from oslo commits:
[2fd457bf2cc] Ignore migrate versioning tables in utf8 sanity check

Change-Id: I6aef126b8d09c7a44f3815c4143ef1d4e5463426
Closes-Bug: #1301036
Merge "Sanitizes authentication methods received in requests." into milestone-proposed
Merge "Sync from oslo db.sqlalchemy.migration" into milestone-proposed
For ldap, API wrongly reports user is in group

When the ldap identity backend is configured,
HEAD v3/groups/​{group_id}​/users/​{user_id}
always returns 200, even if the user is not actually in the group.
This is because the sql and kvs backend will raise NotFound
exception if the user is not in the group, but the ldap backend
just return result.

Change-Id: Ie1585c8aebe054091bd76fded666bf41125ff9ca
Closes-Bug: 1245247
Keystone doesn't use pam

The requirements.txt file had pam, but Keystone doesn't use pam.

Change-Id: Ib617146d4ec75532f994ae85837ecbf383647306
Merge "Keystone doesn't use pam" into milestone-proposed
Remove legacy_endpoint_id and enabled from service catalog

Those two fields are for internal use, and should not be in the token.

The token size was expanding past the threshold where it could
be passed between a wsgi process and Apache HTTPD, even for
a basic, devstack sized catalog.  This reduces the size.

Change-Id: Ic8eb70e519a8a35fd05b497d917f9889e82b6e7f
Closes-Bug: 1302075
Fix invalid LDAP filter for user ID with comma

The Keystone server would respond with a 500 error when configured
to use the LDAP identity backend and a request is made to get a
token for a user that has an ID with a comma. The response is like:

 Authorization Failed: An unexpected error prevented the server from
 fulfilling your request. {'desc': 'Bad search filter'} (HTTP 500)

This is because the user DN wasn't properly escaped in the filter
for the query to get the groups that the user is a member of.

Closes-Bug: #1302106

Change-Id: Ib4886e66af0e979fcf23a84bcd51b07034547cb9
Updated from global requirements

Change-Id: I009a6494637c2daaae7a08e8ed3c6bf13155ead6
Merge "Fix invalid LDAP filter for user ID with comma" into milestone-proposed