The OneLogin SSO App allows administrators to integrate Incident IQ with a local AD server. This will enable districts to automatically populate and update user data in iiQ directly from their AD server.
The following guide is designed to provide step-by-step instructions on how to install the OneLogin SSO Integration app, establish a link with OneLogin for SSO functionality, and set up a nightly task to sync user data with Incident IQ.
Creating an Active Directory User
Before beginning the installation process, you will need to ensure you have the following:
An active directory vendor account that has the following permissions:
Replicating directory changes.
Read.
A machine that runs .NET Framework v.4.5.1 or higher and has network access to your district’s AD server.
Important Note: You will need to complete this step before proceeding. If you are unfamiliar with granting these specific permissions to a user, please refer to the following Microsoft help guide on Giving Users Replicating Directory Changes Permissions.
Installation
To install the OneLogin SSO integration app, begin by selecting Incident IQ Apps > Browse on the left navigation bar. Scroll down to the Single Sign-On section and click on the OneLogin SSO app
On the OneLogin SSO app page, click on Install.
Once the installation has been completed, click on Manage App Settings and continue to the next section to configure your OneLogin SSO installation.
Configuration
On the Overview Tab, select the two options: Enable User Login and Enable User Sync. Before doing anything else, you must check these two options and click Save.
From here, more options appear on the app tabs list. Click on Sync Executable.
This page will assist you in setting up your connector app configuration file. At the very least, you will need to provide the following information:
AD Username (You will want to use the service account created in [section 1] of this document)
AD Password
AD Domain (Example: district.k12.tx.us)
AD Server IP (12.3.4.56)
AD Server Port (Blank for default)
If desired, you may also set up OU exclusions to prevent account information stored within select AD OUs from being brought over during system syncs. Please note that setting up filters is optional and can be updated anytime.
Additionally, you can enable the sync to copy over additional AD Attributes such as Student/Employee ID and Grade if those data points exist in AD. As with OU filters, this setting is optional and can be updated anytime. When finished, click Save.
Once you have completed entering and saved your configuration information, click on Download Executable (Version 2.2) to download the connector app. Please note that you will want to download this connector app to a device that has access to your AD server and runs overnight.
After downloading the connector file, you will want to run a manual sync to test the connection and download user data to Incident IQ. To do this, run the IncidentIQ.Connectors.MicrosoftAd application (ignore the CONFIG and PDB files in this case.) In the connector app window that appears, click Run now.
If the app runs successfully, a user data packet will be sent to Incident IQ that can then be used to run a system sync.
Establishing the IDP/ISP Connection with OneLogin
At this point, you will need to set up the SSO functionality of the OneLogin SSO app. You can find the Incident IQ metadata URL that OneLogin will ask for by clicking on the Download Service Provider Metadata button within the OneLogin SSO app. You can copy the URL from the address bar of the newly opened tab.
Once the connection has been established, you’ll want to copy the following URL from the OneLogin SAML console.
Next, paste this link into the URL field under the Identity Provider Settings tab within the Classlink SSO app within Incident IQ.
Additionally, further down in this tab, you will need to map the SAML attributes required for login. (Usually login_id, username, email, sAMAccountName, etc.)
After this tab has been configured, the Role mappings and Location mappings will need to be completed to map users to locations and roles within iiQ by OUs, groups, or any additional attribute that captures the location or role for each user.
Creating a Scheduled Sync Task
To schedule the sync to occur automatically, you’ll need to create a task in Windows Task Manager. You can do so by searching for Administrative Tools and selecting Task Scheduler. This will open the Task Scheduler window.
In the Task Scheduler window, start by clicking on Action > Create Basic Task...
This will open the Create Basic Task Wizard. At the very least, you will need to provide a name for the new task. You can also add a task if desired. Once complete, click Next.
In the next step, you will be asked to select when this task should Trigger. We recommend running it daily (overnight) for the most accurate user data. Please ensure you set the task to run regardless of whether a user is logged in or not on the server. Once complete, click Next.
For the next step, you will need to specify what action the task will take when running. Select Start a Program and then click on Next.
When specifying the action to perform, locate the file IncidentIQ.Connectors.MicrosoftAd.exe in the Program/script file browser. Supply the argument -usersync in the Add arguments field. And finally, you will need to indicate the path you unzipped the files to in the Start in field. Once complete, click Next.
In the sync properties window, you will need to check Run whether user is logged on or not, as well as Run with highest privileges. Click OK to complete the sync setup.
In the final step, you may review your task’s settings. Once you have completed your review, check Open the Properties dialog for this task when I click Finish option and then click the Finish.
Mapping User Roles and Locations
You will want to log back into the Incident IQ OneLogin SSO app to set your user roles and location mappings. These will indicate automatic role and location assignments for users during system syncs. You can find these settings in the Role Mappings and Location Mappings tabs.
You will want to set a default Role and Location for users immediately. These settings will act as fallback options if a user account does not match any custom mappings you set further down in these tabs. We recommend using the following for these options:
Default Role: You will want to set this to Guest during your initial setup. Once all of your custom mappings have been completed and user roles verified, you will likely want to put this to No Access instead.
Default Role: You will want to either use the Central/District Office location or create another specific location (such as Unassigned) for this.
When mapping roles and locations, you may use groups, OU fragments, location name, or any combination of the three. Please note that you do not have to map locations and roles using the same method.
The custom mappings section allows you to specify your user groups or OUs you wish to utilize for mapping users to their respective roles. Please note, when using OUs, you will want to structure them in the same format as the examples below:
OU=Staff and Faculty
OU=Students
OU=IT Staff
---
Deborah Prosser - Community Manager