Changes

Jump to navigation Jump to search
1,747 bytes added ,  18:39, 29 November 2011
m
no edit summary
Line 23: Line 23:     
View your LDAP Schema, ObjectClasses and Attributes with [[:Phpldapadmin ]]
 
View your LDAP Schema, ObjectClasses and Attributes with [[:Phpldapadmin ]]
 +
 +
If you want to use the LDAP directory of your SME Server as authentication source on third party software, here are the parameter you need
 +
 +
User Base: ou=Users,dc=domain,dc=tld
 +
Group Base: ou=Users,dc=domain,dc=tld
 +
Host: <the ip or hostname of your SME Server> (prefer the hostname or you'll have additional problem with certificate verification)
 +
 +
If you need to setup a filter to display only users, you can use the following:
 +
 +
(&(objectClass=inetOrgPerson)(objectClass=sambaSamAccount))
 +
 +
If you need to setup a filter to display only groups, you can use the following:
 +
 +
(&(objectClass=mailboxRelatedObject)(objectClass=posixGroup))
 +
 +
{{Note box|Most of the time, anonymous bind are sufficient, no need to configure the Admin DN and password. A few applications do requires to bind as a valid user. This is needed when your application requires access to attributes like uidNumber, gidNumber, homeDIrectory, loginSHel etc... (for example, if you need to authenticate another Linux box using nss_ldap or sssd, you'll need to bind as a valid user). In this case, you can create a regular user (you may name it auth for example), set it a password, and use it's dn and credential to bind to your LDAP server}}
 +
 +
{{Note box|The LDAP directory can be consulted with plain text connection, but for security reason, authentication against LDAP is only allowed using SSL or TLS (or if your connection runs directly on SME itself). So if you want to authenticate against LDAP on a remote box, you need to be sure to use LDAPs on port 686, or TLS on port 389. You also need to be sure your application can validate the certificate of your SME Server. If you try to authenticate over a plain text connection, SME will simply reject the authentication}}
    
Example setups for different types of clients
 
Example setups for different types of clients

Navigation menu