Check if encoded user credential may get truncated
In some deployments, user passwords are generated by other
authentication infrastructures where the length of the Base64 encoded
credentials is longer than the DB limit.
This patch checks if the encoded credential might be truncated when
it is generated and fail early during stack creation, or else it will
cause troubles later on when operating the stack.
Don't block stack deletion if user creds fail
In some deployments, user passwords are generated by other
authentication infrastructures where the length of the Base64 encoded
credentials is longer than the DB limit. When this incorrect behavior
happens silently, the user credential can not be retrieved.
In this case, stack deletion will abort due to uncaught exception.
This patch enables a stack deletion to handle this error so that stack
can be properly deleted.
Closes-Bug: #1518903
(cherry picked from commit 0d9af5c6833e26532bf798ebd0756e93d674b7fc)
(cherry picked from commit 9698da68040b0e3ac63c23e72f31d9739c76e03e)
Reviewed: https:/ /review. fuel-infra. org/14135 ci/fuel- 5.1.1-updates/ 2014.1. 1
Submitter: Sergey Kraynev <email address hidden>
Branch: openstack-
Commit: c329b62eee7836c 9c829895d901572 5979e952d5
Author: tengqm <email address hidden>
Date: Wed Jul 6 11:24:58 2016
Prevent using long password for crypting trust
Check if encoded user credential may get truncated
In some deployments, user passwords are generated by other
authentication infrastructures where the length of the Base64 encoded
credentials is longer than the DB limit.
This patch checks if the encoded credential might be truncated when
it is generated and fail early during stack creation, or else it will
cause troubles later on when operating the stack.
Don't block stack deletion if user creds fail
In some deployments, user passwords are generated by other
authentication infrastructures where the length of the Base64 encoded
credentials is longer than the DB limit. When this incorrect behavior
happens silently, the user credential can not be retrieved.
In this case, stack deletion will abort due to uncaught exception.
This patch enables a stack deletion to handle this error so that stack
can be properly deleted.
Closes-Bug: #1518903 32bf798ebd0756e 93d674b7fc) ac63c23e72f31d9 739c76e03e)
(cherry picked from commit 0d9af5c6833e265
(cherry picked from commit 9698da68040b0e3
Change-Id: Icc05b300542006 c3306530949e9fa 6726d76589c