Merge branch 'releases/1.6.5' into develop
Bump next developer version
Consolidate git push commands

[skip ci]
Do not hard code the test account username and password
Add a test case to ensure we can modify the test account name and password
[#71528362] Adjust coverage classpath.
Make sure that the classpath contains all the needed classes. This is easiest done by pointing it to our compile directory.
https://www.pivotaltracker.com/story/show/71528362
https://www.pivotaltracker.com/story/show/70410348
[#70410348]
- Move LDAP libraries to the common module.
- Implement an authentication manager that inserts data into the DB when user is not already there and properly marks the source/origin
- Add all ldap configuration from login-server to allow a ldap profile
- Add two new future fields(origin/externalId) to UaaUser and ScimUser
- Add in embedded LDAP server for testing (mock) only
- Add keystone authentication support
- Refactor Scim and Audit mock tests to properly create and clear out the application context
Only log warn if it's not trying to log the default unset variable
Merge branch 'feature/uaa-ldap-authentication' into develop
https://www.pivotaltracker.com/story/show/70402910
Delivers [#70402910]

Verify that we indeed store failed login attempts in the service.
Enhance IntegrationTestContextLoader to be more like those provided by spring
Enhance IntegrationTestContextLoader with environmentConfigDefaults
Move IntegrationTestContextLoader to common

so that it may be used by the login-server project as well
Attempt to cache maven on Travis

[#71971554] https://www.pivotaltracker.com/story/show/71971554
Attempt to cache APT packages too
Merge branch 'feature/travis_cache' into develop
Update vcap_common gem to 4.0.1

Signed-off-by: Matthew Sykes <matthew.sykes@gmail.com>
Merge pull request #91 from cloudfoundry/gemfile-update

Gemfile update - possibly unused, see https://www.pivotaltracker.com/story/show/72906112
https://www.pivotaltracker.com/story/show/72187802
Finishes [#72187802]
Add origin (user origin column, values like 'uaa', 'ldap', 'keystone') to track where a user originated from during the authentication process
Add external_id to track the users external username, for cases like LDAP, it will be the DN or UID
Implement origin validation during authentication. Meaning, a user can only be authenticated by the UAA authentication manager if the user was originated in the UAA (not LDAP or Keystone or SAML). This is to prevent authentication or non UAA users by the UAA authentication manager.
The default value for a user origin is now UAA. As a result, systems with ldap or saml integration may have to reauthorize approvals as those user will be recreated.

Refactor the authz_approval table to use USER_ID rather than non unique username
The origin/external_id changes are related to refactoring the approvals table relationship.
Merge branch 'feature/origin_and_externalId_columns' into develop