Line 7: |
Line 7: |
| This contribution for smeserver adds LDAP | | This contribution for smeserver adds LDAP |
| | | |
− | {{Warning box|This is development code, not suitable for production servers, testing and feedback is welcome}} | + | {{Warning box|This is development code, not suitable for production servers, testing and feedback is needed}} |
| | | |
| This allows the use of SME user's database in other applications | | This allows the use of SME user's database in other applications |
| : either local, eg. a LAMP app | | : either local, eg. a LAMP app |
− | : on the server itself like egroupware, | + | : on the server itself, eg. egroupware |
− | : on the local network, eg. another server in the local network which runs an ERP, but uses SME server user/group database, | + | : on the local network, eg. another server in the local network which runs an ERP, but uses SME server user/group database |
| : or even a remote host, eg. a GLPI instance used to manage requests from several clients using SME server. | | : or even a remote host, eg. a GLPI instance used to manage requests from several clients using SME server. |
| | | |
− | Some applications have the possibility to use imap/pop authentication (egroupware, GLPI, maybe others), but some don't offer this possibility, but can use only LDAP. imap/pop isn't as powerful as LDAP as we can only check user/password, whereas with LDAP, we can check other attributes, groups of the user etc... | + | Some applications have the possibility to use imap/pop authentication (egroupware, GLPI, maybe others), but some don't offer this possibility, but can use only LDAP. imap/pop isn't as powerful as LDAP as we can only check user/password, whereas with LDAP, we can check other attributes, groups of the user etc. |
| | | |
| === Requirements === | | === Requirements === |