The server profiles store information about your LDAP server (e.g. host name) and what kind of accounts (e.g. users and groups) you would like to manage. There is no limit on the number of server profiles.
Select "Manage server profiles" to open the profile management page.
Here you can create, rename and delete server profiles. The passwords of your server profiles can also be reset.
You may also specify the default server profile. This is the server profile which is preselected at the login page. It also specifies the language of the login and configuration pages.
You can create a new server profile by simply entering its name and password. After you created a new profile you can go back to the profile login and edit your new server profile.
All operations on the profile management page require that you authenticate yourself with the configuration master password.
Please select you server profile and enter its password to edit a server profile.
Each server profile contains the following information:
General settings: general settings about your LDAP server (e.g. host name and security settings)
Account types: list of account types (e.g. users and groups) that you would like to manage and type specific settings (e.g. LDAP suffix)
Modules: list of modules which define what account aspects (e.g. Unix, Samba, Kolab) you would like to manage
Module settings: settings which are specific for the selected account modules on the page before
Here you can specify the LDAP server and some security settings.
The server address of your LDAP server can be a DNS name or an IP address. Use ldap:// for unencrypted LDAP connections or TLS encrypted connections. LDAP+SSL (LDAPS) encrypted connections are specified with ldaps://. The port value is optional. TLS cannot be combined with ldaps://.
LAM includes an LDAP browser which allows direct modification of LDAP entries. If you would like to use it then enter the LDAP suffix at "Tree suffix".
Some LDAP queries are internally cached by LAM. You can specify how long LAM should use cached data. The search limit is used to reduce the number of search results which are returned by your LDAP server.
The access level specifies if LAM should allow to modify LDAP entries. This feature is only available in LAM Pro. LAM non-Pro releases use write access. See this page for details on the different access levels.
LAM is translated to many different languages. Here you can select the default language for this server profile. The language setting may be overriden at the LAM login page.
LAM can manage user home directories and quotas with an external script. You can specify the home directory server and where the script is located. The default rights for new home directories can be set, too.
LAM supports two methods for login. You may either specify a fixed list of LDAP DNs or let LAM search for the DN in your directory. E.g. if a user logs in with the user name "joe" then LAM will do an LDAP search for this user name. When it finds a matching DN then it will use this to authenticate the user. The wildcard "%USER%" will be replaced by "joe" in this example. This way you can provide login by user name, email address or other LDAP attributes.
You may also change the password of this server profile.
LAM supports to manage various types of LDAP entries (e.g. users, groups, DHCP entries, ...). On this page you can select which types of entries you want to manage with LAM.
The section at the top shows a list of possible types. You can activate them by simply clicking on the plus sign next to it.
Each account type has the following options:
LDAP suffix: the LDAP suffix where entries of this type should be managed
List attributes: a list of attributes which are shown in the account lists
On the next page you can specify in detail what extensions should be enabled for each account type.
The modules specify the active extensions for each account type. E.g. here you can setup if your user entries should be address book entries only or also support Unix or Samba.
Each account type needs a so called "base module". This is the basement for all LDAP entries of this type. Usually, it provides the structural object class for the LDAP entries. There must be exactly one active base module for each account type.
Furthermore, there may be any number of additional active account modules. E.g. you may select "Personal" as base module and Unix + Samba as additional modules.