Sync jsonutils from oslo-incubator 32e7f0b5

Syncs the jsonutils module from oslo-incubator using commit
32e7f0b56f527427544050f251999f3de588ac93 .

Note that since there's a feature change in oslo-incubator I'm
switching to module syncs.

 $ ./update.sh --nodeps --base keystone --dest-dir ../keystone \
     --modules jsonutils

This change includes the following commit
-----------------------------------------
d9060f6 Check for namedtuple_as_object support before using it

Change-Id: I152faacdbb394209f87b91a699bb4ca185c2125e
Closes-Bug: #1361230
Keystone local authenticate has an unnecessary pending audit record.

Pending should be used for long running operations but local
authenticate is not such an operation.

Change-Id: If06c826c912a973cf133c6dcc6dabe77a392c64a
Closes-Bug: #1366991
Document mod_wsgi doesn't support chunked encoding

Document in logical places that keystone under mod_wsgi will not
support chunked encoding.

Change-Id: I957059be560fa65e2f0d5166d9490b2c7bab9f17
Closes-Bug: #1346211
LDAP: refactor use of "1.1" OID

I've noticed several people asking questions about the arbitrary usage
of ['1.1'] in code review, so I figured I'd refactor them into a
constant so it's a bit more self-documenting, since it's definition is,
in fact, completely arbitrary:

    If the client does not want any attributes returned, it can specify
    a list containing only the attribute with OID "1.1". This OID was
    chosen arbitrarily and does not correspond to any attribute in use.

Source: http://www.alvestrand.no/objectid/1.1.html

Change-Id: Ib2901bd8593b5a6ea8b6a5488f0d45b51fa8b77c
Make the extension docs a top level entry in the landing page

Currently any documentation about extensions that Keystone offers
is lacking at best. This patch moves the documentation out of the
busy configuration section, and to index/landing page.

It also provides a brief summary for each extension, and a logical
point of entry for additional information.

Change-Id: Ide8ac9b277e0fc9cab9c01073bb72fe3bc369aed
Add V3 JSON Home support to GET /

The server wasn't returning a JSON Home response for GET / when the
Accept header is `application/json-home`. By returning the V3 JSON
Home response for GET / a V3 client that supports JSON Home can
GET either /v3 or / and use the response. The identity API should
be able to be set to /.

Closes-Bug: #1366589
Change-Id: I3191a85acf9d2f582f6b48a164cf5ac2bf84a8cf
Merge "Document mod_wsgi doesn't support chunked encoding"
Merge "Keystone local authenticate has an unnecessary pending audit record."
Merge "LDAP: refactor use of "1.1" OID"
Merge "Sync jsonutils from oslo-incubator 32e7f0b5"
Merge "Add V3 JSON Home support to GET /"
Merge "Make the extension docs a top level entry in the landing page"