AAIRS Explained

AAIRS is an “Automatic Authorization, Integration and Real-Time Synchronization” program.

AAIRS Overview

AAIRS takes care of all authorization and authentication processes for users. The key to AAIRS is that once setup is complete, the authentication and authorization processes are completely automatic and self-sufficient.


AAIRS makes it easy to integrate Tegrity with authentication authorities like CMS, LMS and other institution systems. Recording is easy for instructors, and requires no work for IT as every recording is automatically placed in the right course for enrolled students to access securely.


AAIRS handles all of the authentication and authorization tasks. It integrates with any of the following systems, allowing for single-sign-on access from either Tegrity or your institution’s CMS.

  • Active Directory
  • Canvas
  • Blackboard
  • Angel
  • Desire2Learn
  • eCollege
  • LDAP
  • Moodle
  • Sakai
  • WebCT
  • U/C Builder
  • Excel
  • Self-Registration
  • CSV


Drag-and-drop multiple authorities

It is easy to configure and reconfigure using a graphical interface that allows you to drag-and-drop connectors. AAIRS can connect to multiple authentication authorities and data sets simultaneously.


AAIRS also handles authentication and authorization in real-time so it is always up-to-date.


How it works

AAIRS has 3 modules:

1. Authentication: Verifies that the user is who they claim to be (the username and password are correct). Uses the institution’s own authentication authorities. Can be configured to check one or more authentication authority.

2. Authorization: Runs after a user has been authenticated. This process provides permission for what the user is allowed to see and do in Tegrity. Authorization works to link up each usernames to the courses in which they are enrolled, and also flags each user by role (instructor/student).

3. Interlinks: Automatically publishes direct links to Tegrity in external systems such as Blackboard and Angel.

Who can use AAIRS?

To use AAIRS, customers must be updated to the June 2015 update (at least) and be using the Tegrity Virtual Appliance or the Tegrity Full-Service. Customers using the previous IMS import method need to be converted to AAIRS.

Step 1: How to configure Authentication

In this first step, AAIRS will decide whether or not the username and password credentials entered are valid. In order to do so, Tegrity will connect with your course management system to determine user ID’s. A small amount of setup is required:

1. Access your Tegrity admin dashboard.

2. Click “Manage AAIRS” under the “Integration” heading.

Dashboard Manage AAIRS

3. The following screen appears:

This screen allows you to add multiple connectors (including course management systems). To add an authentication connector:

4. Select “Edit”. The following screen will appear, with all available connectors located on the right-hand side.

5. Simply drag the available connectors from the box on the right into the “Currently Used Connectors” box on the right. Below is an example of inserting Blackboard as an authentication connector.

Your connector will be added. Enter the required information.

Repeat the drag-and-drop process until all desired connectors have been added.

Step 2: How to setup authorization

Now that authentication is complete, authorization must be put into place. This process automatically assigns roles (student/instructor), and deciphers what a user can and cannot see. Like authentication, multiple connectors can be added. Again, like authentication, select “edit” and drag-and-drop the connectors that you would like to add.

Step 3: How to setup interlinks

Configuring interlinks simply means that Tegrity will automatically add a link to Tegrity inside your course management system. To configure your interlinks, use the same drag-and-drop process.

How to test the process

After you have selected the connectors you would like to use, Tegrity allows you to test run the process. Click “test”, as seen below.

Type in user credentials and select “Test”. Below is an example of a failed user test, meaning that the authentication process failed.

Popular Articles

Let Tegrity Know!

We welcome your feedback on how we can improve the Tegrity lecture capture service. Please provide any comments and suggestions to your account management team.