Auth_token middleware doesn't handle v3 tokens correctly

[Henry Nash]

The auth_token middleware needs to be fixed to:

- Cope with the tenant -> project rename
- Understand Domains

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/23401
Committed: http://github.com/openstack/python-keystoneclient/commit/d782a998474d92d4299b4404b69442f0288efc3b
Submitter: Jenkins
Branch: master

commit d782a998474d92d4299b4404b69442f0288efc3b
Author: Henry Nash <email address hidden>
Date: Mon Mar 4 05:05:15 2013 +0000

    Fix auth-token middleware to understand v3 tokens

    Now that the Identity server supports v3 tokens, the auth_token
    middleware should permit the in-line validation of such a token. This
    essentially means just setting any new environment items
    that correspond to the new attributes that may be in a v3 token (such
    as domains), as well as allowing for the slight format differences.

    Most of the work in this change is actually in the unit tests, where
    it was important to try and enable the existing tests to be run against
    an auth_token middleware configured for both v2 and v3. This meant
    restructing the test class so that the token format is separated
    from the individual tests and is initialized by the class Setup().

    Since there are some new signed token formats included in this testing,
    a new set of the signed tokens was generated.

    Fixes Bug #1132390

    Change-Id: I78b232d30f5310c39089fbbc8e56c23df291f89f