Allow configuration of multiple SAML providers
https://www.pivotaltracker.com/story/show/76918956

cf-properties.yml:
  Allow any configuration under login.saml to be merged in, even child objects
spec:
  Document spec file and deprecate not used properties
  Add in socket options for SAML HTTP metadata requests
login.yml.erb:
  Support new configuration options
  Represent long strings in a cleaner format,
  without the need for duplicate line feeds
Clean up configuration
Simplify by using one liners instead of blocks
Upgrade to Apache Tomcat 7.0.55 for UAA and Login
https://www.pivotaltracker.com/story/show/77973520
Ability to configure default user scopes from a configuration file.
https://www.pivotaltracker.com/story/show/70602010
[#70602010]
Switch login job to look at uaa.login.client_secret only

This allows removal of the uaa.clients.login.secret from the login job spec,
thereby allowing the default UAA login client definition [1] to take place, if
the login client isn't present in the manifest, making login similar to other
default uaa clients.

When uaa.clients.login.secret is present in the login job spec, colocating UAA
and login on the same machine, and not specifying uaa.clients.login results in
an incorrect configuration for the login client in the uaa configuration.

This also allows for removal of clients that are specific to Pivotal's deploy
from deployment manifests without breaking default clients.

https://www.pivotaltracker.com/story/show/70411516

[1] https://github.com/cloudfoundry/cf-release/blob/master/jobs/uaa/templates/uaa.yml.erb#L80-L89
UAA login client redirect-url should look at login.url property
https://www.pivotaltracker.com/story/show/70412024
Upgrade UAA / Login Server
UAA Version 1.8.3
Login Server Version 1.8.5