View Categories

SSO Login

This Feature uses Google Firebase and allows the login with Google, Firebase Email and Password, Facebook, and Github

Setup #

First a Firebase project needs to be created within Firebase, then Disciple.Tools will need to be configured.

Firebase App Config #

Create a firebase project on https://console.firebase.google.com with any name. Analytics is not needed.

Web app #

From the dashboard click “add app” and choose “web”. Choose any nickname. Save the settings that look like this. We’ll need them later.

const firebaseConfig = {
  apiKey: "AIza-***",
  authDomain: "disciple-tools-auth.firebaseapp.com",
  projectId: "disciple-tools-auth",
  storageBucket: "disciple-tools-auth.appspot.com",
  messagingSenderId: "*********",
  appId: "******"
};

Authentication #

From the Left Side Menu select Build then select Authentication.

On the Authentication tab, add the providers you want to enable (Google, Email and Pass, Facebook, etc).

Google example:

Click Add new provider. Then Google. Enable the Provider. Choose a name that users will see, like “disciple-tools-auth”.

Allowed Domains #

Go to the Settings tab. Under Authorized Domain, add the domain of your D.T instance. Examples: “disciple.tools” or “*.disciple.tools”

D.T setup #

Head over Settings (D.T) > SSO Login. On a Multisite

Disciple.Tools can be set up as a Single Site or as a Multisite.With a multisite, the same user can log into multiple instances or version of Disciple.Tools using the same username and password. A single site will give you an instance where you and your users can collaborate on contacts, groups, and more. All your contacts will be in one place and are managed by the Admin and Dispatchers.This is a great starting point if you are a small team working in together over one region. But suppose you have a team in New York with a Facebook Ministry and a team in Chicago with a cool Website and another team in a different location doing campus ministry. It soon become overwhelming to have all the contacts one spot. This is why you might want to separate the teams out into different instances using WordPress as a multisite.The Serve could be set up like this: ministry.com – a D.T instance, or a front facing webpage new-york.ministry.com – instance for the New York team chicago.ministry.com – instance for the Chicago team etc You may choose to have a different instance for each location you are in. You can also separate based on teams, language, media page, etc.

, with the D.T Multisite

Disciple.Tools can be set up as a Single Site or as a Multisite.With a multisite, the same user can log into multiple instances or version of Disciple.Tools using the same username and password. A single site will give you an instance where you and your users can collaborate on contacts, groups, and more. All your contacts will be in one place and are managed by the Admin and Dispatchers.This is a great starting point if you are a small team working in together over one region. But suppose you have a team in New York with a Facebook Ministry and a team in Chicago with a cool Website and another team in a different location doing campus ministry. It soon become overwhelming to have all the contacts one spot. This is why you might want to separate the teams out into different instances using WordPress as a multisite.The Serve could be set up like this: ministry.com – a D.T instance, or a front facing webpage new-york.ministry.com – instance for the New York team chicago.ministry.com – instance for the Chicago team etc You may choose to have a different instance for each location you are in. You can also separate based on teams, language, media page, etc.

plugin, go to the Network Admin > Disciple.Tools > SSO Login.

Open the Firebase tab.

Form the firebaseConfig above, add the apiKey value AIza… to the Firebase API Key, the projectId value to Firebase Project ID and appId to Firebase App ID. Click save.

On the General tab, set the Enable Custom Login Page to “on” and save.

On the Identity Providers tab set the “Google” provider to “on” and save.

Log out and give it a try!

Troubleshooting #

  • Error message “Class “Firebase\JWT\Key” not found may indicate an old version of the mobile app plugin is being used.