forked from haraka/Haraka
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
o Clean-up docs and ready for pkging.
- Loading branch information
root
committed
Aug 18, 2013
1 parent
d6d72b7
commit ee93330
Showing
3 changed files
with
49 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,27 +1,44 @@ | ||
auth/auth_ldap | ||
============== | ||
|
||
The `auth/auth_ldap` plugin... | ||
The `auth/auth_ldap` plugin uses an LDAP bind to authenticate a user. Currently | ||
only one server and multiple DNs can be configured. If any of the DN binds succeed, | ||
the user is authenticated. | ||
|
||
Configuration | ||
------------- | ||
|
||
Configuration is stored in `config/auth_ldap.ini` and uses the INI | ||
style formatting. | ||
|
||
are only two methods supported : `CRAM-MD5` and `LOGIN`. Be aware, the LOGIN | ||
method is highly unsecure and can be used normaly only for local communication. | ||
We stronly recommend only `CRAM-MD5` to be used. | ||
Only the `LOGIN` authentication method is supported assuming that passwords in the | ||
LDAP database are not stored in cleartext (which would allow for CRAM-MD5). Note | ||
that this means passwords will be sent in the clear to the LDAP server unless | ||
an ldaps:// conection is used. | ||
|
||
Current configuration options in [core] are: | ||
|
||
server - the url of the LDAP server (ldap:// or ldaps://) | ||
|
||
timeout - time in miliseconds to wait for the server resonse before giving up | ||
|
||
rejectUnauthorized - boolean (true or false) as to whether to reject connections | ||
not verified against a CA. Meaning, a "false" allows non-verified. | ||
|
||
Example: | ||
[core] | ||
methods=LOGIN,CRAM-MD5 | ||
|
||
server=ldaps://ldap.opoet.com | ||
timeout=5000 | ||
rejectUnauthorized=false | ||
|
||
Users are stored in the `[users]` section. | ||
The [dns] section (that is plural DN and not domain name system), is a list of DNs to use | ||
to bind. The "%u" in the strings is substituted with the user name used in the SMTP | ||
authentication. Note that the keys have no meaning and the DNs are tried in series until | ||
the first successful bind. The LDAP RFC does not allow for parallel binds on a connection, | ||
so it is suggested that the most commonly used DN be placed earlier in the list. | ||
|
||
Example: | ||
[dns] | ||
dn1=uid=%u,ou=Users,dc=opoet,dc=com | ||
dn2=uid=%u,ou=people,dc=opoet,dc=com | ||
|
||
[users] | ||
user1=password1 | ||
user@domain.com=password2 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters