auth_token middleware should not require OS-SIMPLE-CERT extension for v3

[Brant Knudson]

The auth_token middleware will use the /v3/OS-SIMPLE-CERT/ if it's configured to use v3 or if it discovers that v3 is available. OS-SIMPLE-CERT is an extension may not be enabled, so the auth_token middleware shouldn't require it and it must be able to work without it.

http://git.openstack.org/cgit/openstack/keystonemiddleware/tree/keystonemiddleware/auth_token.py?id=9355d279216da8981ee6c31013b3dc16e5355257#n1576

[Dolph Mathews (dolph)]

auth_token should (technically) be able to fallback to purely online validation if any aspect of offline validation fails.

[Morgan Fainberg (mdrnstm)]

I 100% agree with dolph.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/131036

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/131036
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=136f85c01ad4da01f9e073619f22eed5ca2378cc
Submitter: Jenkins
Branch: master

commit 136f85c01ad4da01f9e073619f22eed5ca2378cc
Author: wanghong <email address hidden>
Date: Mon Oct 27 15:12:05 2014 +0800

    fallback to online validation if offline validation fails

    Authmiddleware should fallback to purely online validation when
    fetching certificate config failed or fetching revocation list failed.

    Change-Id: I532e667cc26bbeb9bbd03605b9fb7ea7ebf14afa
    Closes-Bug: #1384898