aboutsummaryrefslogtreecommitdiffstats
path: root/keystone-moon/releasenotes/notes/revert-v2-token-issued-for-non-default-domain-25ea5337f158ef13.yaml
diff options
context:
space:
mode:
Diffstat (limited to 'keystone-moon/releasenotes/notes/revert-v2-token-issued-for-non-default-domain-25ea5337f158ef13.yaml')
-rw-r--r--keystone-moon/releasenotes/notes/revert-v2-token-issued-for-non-default-domain-25ea5337f158ef13.yaml12
1 files changed, 12 insertions, 0 deletions
diff --git a/keystone-moon/releasenotes/notes/revert-v2-token-issued-for-non-default-domain-25ea5337f158ef13.yaml b/keystone-moon/releasenotes/notes/revert-v2-token-issued-for-non-default-domain-25ea5337f158ef13.yaml
new file mode 100644
index 00000000..cc28c7f3
--- /dev/null
+++ b/keystone-moon/releasenotes/notes/revert-v2-token-issued-for-non-default-domain-25ea5337f158ef13.yaml
@@ -0,0 +1,12 @@
+fixes:
+ - >
+ [`bug 1527759 <https://bugs.launchpad.net/keystone/+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.