GivenName mandatory in FusionDirectory for the user but not mandatory in openldap schema

Descriptive title for this enhancement

GivenName mandatory in FusionDirectory for the user but not mandatory in openldap schema, and in some case givenName is not used in some LDAP directories so this cause an issue

Actual behavior

Actually givenName is mandatory in FusionDirectory because its used in the creation of the cn of the user, see field «CN pattern» in configuration.

Expected behavior

Make givenName optional if the option is selected in the FusionDirectory Config

Step by step description of new behaviour

1. Add a checkbox to select if givenName is mandatory or not
2. The checkbox should be selected by default meaning givenName is mandatory, to not change the actual way of working
3. If checkbox is not selected it means givenName is not mandatory
4. If checkbox is not selected we should check «CN pattern» in configuration and trigger an error if %givenName% is used

Benefits

allow people that need to have a blank givenName to be able to use FusionDirectory, the need has been discussed with a customer

Possible Drawbacks

Difficulties with checking «CN pattern» in configuration and interface where we have to remove the red asterisk within givenName on the user interface