Adding extra Spring jar dependency (spring-security-ldap)
First shot on LDAP encryption via LDAPAdmin

Still TODO: refactor (DRY).
LDAP password encryption

Adding a test suite (not implemented yet)
Ignoring eclipse generated files
Adding extra Spring jar dependency (spring-security-ldap)
First shot on LDAP encryption via LDAPAdmin

Still TODO: refactor (DRY).
LDAP password encryption

Adding a test suite (not implemented yet)
Ignoring eclipse generated files
LDAPAdmin: adding dependency to encrypt passwords

Activating also some extra amven plugins to make various test reports
LDAPAdmin - XMLL'inting pom.xml
Merge remote-tracking branch 'mine/encrypting_passwords' into encrypting_passwords

Conflicts:
	.gitignore
	ldapadmin/pom.xml
Merge branch 'master' into encrypting_passwords

Conflicts:
	.gitignore
Merge remote-tracking branch 'pmauduit/encrypting_passwords' into encrypting_passwords

Conflicts:
	.gitignore
Merge branch 'master' into encrypting_passwords
ldapadmin - Bumping to version 3.3 of maven-site

See https://issues.apache.org/jira/browse/HADOOP-10092 (similar issue)
update GN submodule
security-proxy - ignores non HTTPS request check

The security-proxy can bypass CAS authentication in case of specific
user-agents and a HTTP basic-auth is provided. But the filter discards
requests that are not targetted onto https.

This adds an option to ignore if the request targets or not an HTTPS
server (anyway, the geOrchestra instances spread over multiple servers
should be bound over a trusted network, so the risk of sniffing
passwords *should* be mitigated).
Merge remote-tracking branch 'origin'
security-proxy - returns earlier in case of 403|404 error code (#506)

the Security-Proxy provides some specific JSPs for 403 and 404, but
before this commit, the proxified response for 403 / 404 were returned.

Forcing JSPs in case of 404 / 403 upstream responses.

Tested:
- locally
- on intra-test (Rennes Métropole)
ldapadmin - Preparing testsuite on new account creation