Swift proxy is currently rejecting valid v3 tokens because it is
failing to validate them due to its credentials being in the v2
format and missing domain information. This change examines the
version of the API keystone has advertised down the identity-service
relation and configures the proxy conf appropriately
Reviewed: https:/ /review. openstack. org/371554 /git.openstack. org/cgit/ openstack/ charm-swift- proxy/commit/ ?id=5b8b04a2133 cbaad84bf7d4bb5 8801c28f66a938
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5b8b04a2133cbaa d84bf7d4bb58801 c28f66a938
Author: Liam Young <email address hidden>
Date: Fri Sep 16 13:53:13 2016 +0000
Fix support for Keystone v3 API
Swift proxy is currently rejecting valid v3 tokens because it is
failing to validate them due to its credentials being in the v2
format and missing domain information. This change examines the
version of the API keystone has advertised down the identity-service
relation and configures the proxy conf appropriately
Change-Id: Id2215168ffbad1 caf0e7203ded26c 41913181306
Closes-Bug: 1624304