opsi Version 3.3.1 - opsi Download - uib

9.2.1. Integrating the LDAP-backend
9. opsi data storage (backend)
To activate the LDAP-backend change the following settings in
'/etc/opsi/backendmanager.conf':
Settings for the file-backend:
self.backends[BACKEND_FILE] = { 'load': True }
self.backends[BACKEND_LDAP] = { 'load': False }
Settings for the LDAP-backend:
self.backends[BACKEND_FILE] = { 'load': False }
self.backends[BACKEND_LDAP] = { 'load': True }
9.2.2. Configuring the LDAP-backend
self.backends[BACKEND_LDAP]['config'] = {
"host": "localhost",
"bindDn": "cn=admin,%s" % baseDn,
"bindPw": "password",
}
9.2.3. Assign the LDAP-backend to methods
self.defaultBackend = BACKEND_LDAP
self.clientManagingBackend = [ BACKEND_DHCPD, BACKEND_LDAP ]
self.pxebootconfBackend = BACKEND_OPSIPXECONFD
self.passwordBackend = BACKEND_FILE31
self.pckeyBackend = BACKEND_FILE31
self.swinventBackend = BACKEND_MYSQL
self.hwinventBackend = BACKEND_MYSQL
self.loggingBackend = BACKEND_FILE31
In this example the LDAP backend is set as the default backend. The PC-keys and the
pcpatch-passwords are still administrated as files.
Now restart the opsi config daemon 'opsiconfd':
/etc/init.d/opsiconfd restart
The following command creates the LDAP base structure:
opsi-admin -d method createOpsiBase
Underneath the LDAP-base node is an organizationalRole cn=opsi (e.g. cn=opsi,
dc=uib, dc=local). You find underneath the node opsi all of the opsi data. This structure
113