[LDAP] Select more generic objectclass and attributes to configure realms in ldap

[clement-dufaure]

Avoid using attributes 'inseePropriete" for instance

[micedre]

We could use info attribute defined in RFC4524 with a fixed format (key=value).

This attribute could be on an organizationalEntry

This would look like that :

dn: ou=Liens,o=insee,c=fr
objectClass: extensibleObject
objectClass: organizationalUnit
objectClass: top
ou: Liens
description:: TsOpY2Vzc2FpcmUgcG91ciDDqXZpdGVyIGxlcyBtZXNzYWdlcyBkJ2VycmV1ci
 Bzb3VzIE91dGxvb2s=
info: organizationSource=ou=orgs,o=insee,c=fr
info: userSource=ou=users,o=insee,c=fr

An another way, would be to have the attribute and separator configurable.

[micedre]

Instead of forcing a schema, we could also add some configuration key to manage this. We would need some configuration for the LdapRealmProvider and the LdapStoreProvider (Reader or Writer).

LdapRealmProvider

add some configuration in properties with :

• objectclass to search for Realms and/or UserStorage (and to use when creating realm)
• attribute mapping (between userSource and ldap config)

LdapStoreProvider

Either one configuration per realm (more flexible) or one configuration for the provider (subtext : in the same sugoi execution we manage all ldap in the same way)

• map ldap attribute to an entity attribute (we need some special care around properties like username, mail...) (and the format ??)
• decide wich objectclass to search for
• which objectclass to use when creating entities