From 39f6fefca1998a8e4ffb9b2c119780251a3a2124 Mon Sep 17 00:00:00 2001 From: Morgan Fainberg Date: Thu, 7 Jan 2016 16:42:23 -0800 Subject: [PATCH] Add release note for revert of c4723550aa95be403ff591dd132c9024549eff10 Change-Id: I5d3a235c0b4c8ba934795c92bccb207393974ad3 --- ...sued-for-non-default-domain-25ea5337f158ef13.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 releasenotes/notes/revert-v2-token-issued-for-non-default-domain-25ea5337f158ef13.yaml diff --git a/releasenotes/notes/revert-v2-token-issued-for-non-default-domain-25ea5337f158ef13.yaml b/releasenotes/notes/revert-v2-token-issued-for-non-default-domain-25ea5337f158ef13.yaml new file mode 100644 index 0000000000..cc28c7f359 --- /dev/null +++ b/releasenotes/notes/revert-v2-token-issued-for-non-default-domain-25ea5337f158ef13.yaml @@ -0,0 +1,12 @@ +fixes: + - > + [`bug 1527759 `_] + Reverted the change that eliminates the ability to get + a V2 token with a user or project that is not in the + default domain. This change broke real-world deployments + that utilized the ability to authenticate via V2 API + with a user not in the default domain or with a + project not in the default domain. The deployer + is being convinced to update code to properly handle + V3 auth but the fix broke expected and tested + behavior.