University Policies

Page tree

Versions Compared

Old Version 8

changes.mady.by.user O'Neill, Erin E.

Saved on

compared with

New Version 9

changes.mady.by.user O'Neill, Erin E.

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Integration Levels

    1. Course: The integration installation is bound to the course only and does not impact parts of the LMS system beyond the course.

    2. Account: The integration installation is bound to the account level in the LMS and impacts any courses associated with the account. This level requires sufficient testing to ensure that courses associated with the given account are not negatively impacted.

    3. System: The integration installation is bound to the entire system or root level in the LMS and impacts all users and courses. This level requires the most testing and vetting to ensure that courses and users across the entire system are not negatively impacted.

    4. Pass-Through vs. Deep Integration

      1. Pass-Through: The integration installation and functionality is such that it serves as a single sign-on feature for its users where all functionality other than authentication is controlled by the third-party system. Effectively, the LMS passes user credentials to the integration’s application.

      2. Deep: The integration installation and functionality allows two-way data transmission between the LMS and the third-party application (e.g., grading information is shared for assignments).

  2. LTI: The integration employs the IMS Global Learning Consortium Learning Tools Interoperability (LTI) standard. This is a standard protocol for secure data exchange between any Learning Management System and another software. 

  3. API: The integration employs the Application Programmer Interface (API) often required for a Deep integration. API integrations require system authorization, thorough security evaluation, and significant testing.

  4. Single Sign-On (SSO): An authentication process that allows a user to log in with a single ID and password to any of several related, yet independent, software systems. For LMS third-party integrations, log in happens when users access the LMS. Integrations that employ SSO receive user authentication credentials from the LMS.

Refer to the Rowan University Technology Terms and Definitions for all other terms and definitions that are used in this policy.

...