How do I manage an LDAP connection?

Active Directory is a directory service that many schools use in order to establish security rules on their servers and store data in a hierarchical format.  We utilize LDAP (Lightweight Directory Access Protocol) in order to pull this data into the CrisisGo app from an organization’s Active Directory.  Examples of the data that we would pull are:

  • Staff Names
  • Staff Roles
  • Contact Information
  • Staff ID’s (used to link to class rosters)

Here are some videos that give a tutorial and explanation on LDAP:

An example of how a school’s data is stored within their Active Directory can be seen below:

To set up a new CrisisGo LDAP connection, log into the Console for the applicable school.  From here, navigate to User/Role, then click the LDAP Users tab.  Then click the New LDAP button as seen below:

From here, you will be taken to the screen to enter all applicable information regarding the user’s AD.  This information will be provided by the organization.  Please note that the port will always be 389 and all fields with a red asterisk are mandatory:

After all applicable information has been entered, click Save.  From the next menu, verify that all of the correct information is displayed and click the LDAP Security Group icon under the Actions menu:

The next screen will allow you to map the school’s Security Groups with a CrisisGo Role.  This will determine what alert checklists each user will have access to.

Click Save.  On the LDAP Users menu, click on the Show LDAP Data button:

Next, click on Synchronize to manually pull the user data into the CrisisGo Console:

Verify that the data has been pulled over.  Clicking Publish will push the data out to the CrisisGo app. 

You can always verify that data is syncing regularly by navigating to this menu and checking the WhenChanged field.  This will display the timestamp of the last successful sync:

Note – LDAP connection requests will come from the following IPs:

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.