add saml_login/cf-release info to the doc
add one more user for verification purposes
ldap database(openldap) and sample entries
ignore preview files
adjust for openldap
sample ldap configurations
Squashed commit of the following:

commit 3c9579a5b38f3495917e68d6777563fbef178eb3
Author: Filip Hanik <fhanik@gopivotal.com>
Date:   Mon Jan 20 17:26:32 2014 -0700

    Running into
    http://forum.spring.io/forum/spring-projects/security/114612-multiple-authentication-managers-defined-but-only-the-last-one-is-applied
    https://jira.springsource.org/browse/SEC-1937

    putting ID for one authentication-manager and alias for the other, makes ldap and saml login both work

commit 924721a1f7b4a9194e14438f1086c2626c7787da
Author: Filip Hanik <fhanik@gopivotal.com>
Date:   Mon Jan 20 16:12:31 2014 -0700

    break out SAML related beans into it's own profile, so that it's presence can be controlled through manifest options
fix the ability to use an ID for the authentication manager.
align with the convention of testing passwords
Allow the saml-login server, when deployed within Eclipse to have the same context root as when deployed with mvn tomcat:run -Pintegration
when running integration tests, the provider is Bouncy Castle, and the errors are slighgtly different
start adjusting the logs for better output
minor update to the documentation. break out OpenAM set up into it's own document
advance version forward
align files from login-server to saml-login server. saml-login will become the new login-server when consolidated
remove the original login-server, we will replace it with the saml-login-server
moved saml-login-server into login server to be the main server
adjust the POM files for the removal of login-server and the renaming of saml-login-server to login-server
break out existing UI code into it's own branded directory, called ooss
remove the pivotal-login-server, and create the branded pages in login-server under the brand pivotal, controlled by login.brand property