When using profile=ldap, we allow a chained authentication mechanism.
The user authentication will first be attempted against the UAA for boot strap users, or users created with the scim endpoints.
If that authentication fails, we attempt an LDAP authentication.
Display the username instead of the principal.
Merge branch 'feature/chained_ldap_uaa_authentication' into develop
Deploy scripts exit properly if usage is wrong
Bump release version to 1.6.3
Merge branch 'releases/1.6.3' into develop
Bump next developer version
Consolidate git push commands

[skip ci]
Implement test methods for password comparison.
Upgrade the LDAP API model because of https://issues.apache.org/jira/browse/DIRSERVER-1884
Attempt at setting up a basic ldap

[#68008022] https://www.pivotaltracker.com/story/show/68008022
sudo as necessary

[#68008022] https://www.pivotaltracker.com/story/show/68008022
quiet the ldap setup

[#68008022] https://www.pivotaltracker.com/story/show/68008022
move ldap scripts

[#68008022] https://www.pivotaltracker.com/story/show/68008022
Add ldap config to manifest when using ldap profile

[#68008022] https://www.pivotaltracker.com/story/show/68008022
Unfancy the shell

[#68008022] https://www.pivotaltracker.com/story/show/68008022
Adding in a keystone profile as well.
Complete the ldap install with an optional TLS setup
Skip Forgot/Change password integration tests when keystone is active

[#68008022] https://www.pivotaltracker.com/story/show/68008022
Fix the reset password test for keystone(ignore)
Add saml meta data for the boot strap test to work properly
Ignore ResetPasswordControllerIntegrationTests when ldap is active
Configure for local ldap