[], /* 'attr_display_order' => [ 'givenName', 'sn', 'cn', 'displayName', 'uid', 'uidNumber', 'gidNumber', 'homeDirectory', 'mail', 'userPassword' ], */ /* |-------------------------------------------------------------------------- | Custom Date Format |-------------------------------------------------------------------------- | | Configuration to determine how date fields will be displayed. | */ 'datetime_format' => 'Y-m-d H:i:s', /* * These attributes will be forced to MAY attributes and become optional in the * templates. If they are not defined in the templates, then they wont appear * as per normal template processing. You may want to do this because your LDAP * server may automatically calculate a default value. * * In Fedora Directory Server using the DNA Plugin one could ignore uidNumber, * gidNumber and sambaSID. * # 'force_may' => ['uidNumber','gidNumber','sambaSID'], */ 'force_may' => [], /* * If 'login,attr' is used above such that phpLDAPadmin will search for your DN * at login, you may restrict the search to a specific objectClasses. EG, set this * to array('posixAccount') or array('inetOrgPerson',..), depending upon your * setup. */ 'login' => [ 'attr' => [env('LDAP_LOGIN_ATTR','uid') => env('LDAP_LOGIN_ATTR_DESC','User ID')], // Attribute used to find user for login 'objectclass' => explode(',',env('LDAP_LOGIN_OBJECTCLASS', 'posixAccount')), // Objectclass that users must contain to login ], ];