Difference between revisions of "LDAP Authentication"
m (→Source) |
m (→Description) |
||
| 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 | + | {{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 | + | : 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 === | ||
Revision as of 06:43, 8 October 2008
LDAP for SME Server
Maintainer
Description
This contribution for smeserver adds LDAP
This allows the use of SME user's database in other applications
- either local, eg. a LAMP app
- 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
- 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.
Requirements
You need a test server, preferably SME 8.
We need feedback to Bugzilla, either here or create a new bug for new issues.
Installation
This contrib is currently held in the smetest repository, so the following commands will install on your smeserver.
yum --enablerepo=smetest install e-smith-base+ldap e-smith-samba+ldap
This will replace standard e-smith-base and e-smith-samba packages
signal-event post-upgrade; signal-event reboot
Uninstall
rpm -e e-smith-base+ldap e-smith-samba+ldap yum install e-smith-base e-smith-samba [untested ...]
Usage
ToDo, Add example setups for different types of clients
Source
The source for this contrib can be found in the SME Server CVS e-smith-base+ldap and e-smith-samba+ldap on sourceforge.
Bugs
Please raise bugs under the SME-Contribs section in bugzilla and select the smeserver-? component or use this link .
