{"id":47214,"date":"2020-05-20T10:04:40","date_gmt":"2020-05-20T09:04:40","guid":{"rendered":"https:\/\/churchtools.academy\/help\/non-knowledgebase\/uncategorized\/ldap-service\/"},"modified":"2026-03-18T16:06:34","modified_gmt":"2026-03-18T15:06:34","password":"","slug":"ldap-service","status":"publish","type":"docs","link":"https:\/\/churchtools.academy\/en\/help\/system-settings\/ldap-login-systemsettings\/ldap-service\/","title":{"rendered":"LDAP service"},"content":{"rendered":"\n

The ChurchTools LDAP service works as an LDAP server<\/a> and makes all persons and groups available via LDAP access. <\/p>\n\n\n\n

Alternatively, ChurchTools can also authenticate users against an existing LDAP server. For more information, see LDAP integration<\/a>. <\/p>\n\n\n\n

Many software with user rights etc. can use LDAP for authentication (check for valid user name and password) and authorization (which rights). This means that further software use can be controlled via ChurchTools. So there is only ONE password for everything! <\/p>\n\n\n\n

For example, you could configure a congregation’s firewall so that as soon as a person receives the “Graphics” group in ChurchTools, the person can dial into the congregation via VPN<\/a> and access the corresponding network drive. <\/p>\n\n\n\n

Which is already working well: The connection with NextCloud. NextCloud then pulls all groups via LDAP and also detects when I am in a group. A shared folder can then be created for each group, for example, which is automatically available to me if I am in the technical team, for example. <\/p>\n\n\n\n

For NextCloud see Connecting Nextcloud to the ChurchTools Login<\/a><\/span><\/p>\n\n\n\n

For OwnCloud see Setting up OwnCloud<\/a><\/span><\/p>\n\n\n\n

Setup<\/h2>\n\n\n\n

The LDAP service can be transacted directly in the ChurchTools license settings.<\/p>\n\n\n\n

The next step is to create a user with the following data and permissions in your ChurchTools:<\/p>\n\n\n\n