OAuth between two ChurchTools systems

3 Min. lesen

In this guide, we will show you how to link two ChurchTools systems together. One of the two systems serves as an authentication server for the other system, the client. This means that users of the server system can then sign up to the client system. They do not need separate login data on the client.

1. Prepare the OAuth server #

Let’s first look at how to add a client to your OAuth server. In the ChurchTools system, navigate to the Login page that will serve as the server. This is the system on which the users who are to be able to sign up to the second system already exist. We describe how to reach the Login page on Login to ChurchTools.

Click on the Add OAuth client 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”.

System settings - General - Login - Add OAuth-Client

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) .

The redirect URI is of course missing, as it is provided by the client and must then be entered here.

System settings - General - Login - Add OAuth-Client - Client parameter

2. Configure the OAuth client #

Now switch to your client system and open the Login page there too. Open the following input mask via the Add OAuth server button. Enter the relevant data from the server here.

In the lower section of the input mask, you can use the Create new persons button to define whether persons who do not yet exist on the client are created when they sign up via the server using OAuth. You must then define which person status they receive and which department and campus they are assigned to.

System settings - General - Login - Edit OAuth server

If it is important for your connection to the authentication server, fill in the Client secret field. You can freely assign a password here. No client secret is currently required for the connection to a ChurchTools server.

Finally, copy the client identifier.
Your work on the client is now completed.

3. Finalize the OAuth server #

Add redirect URI #

To complete the connection between the two ChurchTools systems, enter the redirect URI on the server’s Login page. Use the Add redirect URI button to open the corresponding window and enter the link copied from the client here.
All the data required for the connection between the server and client has now been entered.

Assign necessary permission #

In order for users of your ChurchTools server to be able to sign up to the ChurchTools client via OAuth, you need the permission Log in to external system via ChurchTools account (Login to External System). You can find this permission in the rights management in the Administration section. You can find more information on this on our Login to ChurchTools help page.

Login to the client #

The option to log in via the authentication server is now displayed in the client login screen. The standard login for ChurchTools may be hidden and therefore no longer visible.

ChurchTools - Log in with

If you select this option, a window will open informing you which login information will be passed on from the server to the client. If you agree, you will be logged in to the client system.

ChurchTools - Log in with - pass information
Aktualisiert am 30. January 2026
Was this page helpful for you?