{"id":45112,"date":"2026-06-08T10:00:00","date_gmt":"2026-06-08T09:00:00","guid":{"rendered":"https:\/\/churchtools.academy\/help\/non-knowledgebase\/uncategorized\/oauth-between-two-churchtools-systems\/"},"modified":"2026-06-22T15:25:58","modified_gmt":"2026-06-22T14:25:58","password":"","slug":"oauth-authentication-with-churchtools","status":"publish","type":"docs","link":"https:\/\/churchtools.academy\/en\/help\/system-settings\/oauth-login-systemsettings\/oauth-authentication-with-churchtools\/","title":{"rendered":"OAuth Authentication with ChurchTools"},"content":{"rendered":"\n

In this guide, we’ll show you how to link two ChurchTools systems<\/strong> together. One of the two systems serves as the authentication server for the other system, the client. This means that users of the server system can then log in to the client system. They do not need separate Login credentials for the client. <\/p>\n\n\n\n

You can also use this page as a guide if you want to use a third-party system<\/strong> instead of a second instance of ChurchTools. For example, you could use your ChurchTools as an authentication server for a system like NextCloud, or integrate a different authentication server with your ChurchTools. The configuration in ChurchTools remains the same.
Unfortunately, we cannot provide instructions for the other system. Please refer to the help resources provided by the respective software. <\/p>\n\n\n\n

1. Prepare the OAuth server<\/h2>\n\n\n\n

First, let’s look at how to add a client to your OAuth server. In the ChurchTools system, navigate to the Login page<\/em> that will serve as the server. This is the system where the users who will be able to log in to the second system are already registered. We describe how to access the Login page in the section \u201cLogging In to and with ChurchTools<\/a>.\u201d <\/p>\n\n\n\n

Click on the Add OAuth client<\/strong> button. A window opens in which you must give the client a name. You can freely choose the name, it only serves as a unique identifier on the server. In our example, it is called “ChuToo Client”. <\/p>\n\n\n\n

\"Screenshot<\/a><\/figure>\n\n\n\n

ChurchTools now creates all the server information that is relevant for a connection. You can find a simplified explanation of the terms used on our help page What is OAuth? (Login to third-party systems) <\/a>.<\/p>\n\n\n\n

The redirect URI is of course missing, as it is provided by the client and must then be entered here.<\/p>\n\n\n\n

\"Screenshot<\/a><\/figure>\n\n\n\n