
This article will be most useful for IT/IS staff and Concourse admins.
Overview
Concourse is able to integrate with institutions’ Single Sign-On and Learning Management Systems to provide an immersive, intuitive, and familiar experience for end users. Institutions that integrate Concourse with their SSO portal allow users to select a Concourse link within the portal to arrive at their Concourse dashboard and search for syllabi to view or edit. Institutions are able to integrate Concourse with their SSO portals via SAML, CAS, or Shibboleth; as of July 2024, Concourse can no longer accept data transmission from institutions that use LDAP as an authentication option.
Deprecating LDAP
LDAP (Lightweight Directory Access Protocol) is an authentication method that can be used in conjunction with other systems, like Active Directory, to provide single sign-on (SSO) and federated identity management. LDAP requires that credentials, including passwords, be shared during data transmission. As of July 2024, Concourse’s middleware partner Apidapter no longer supports LDAP. Instead, Apidapter supports authentication from other types of SSO, such as SAML, CAS, and Shibboleth, because they do not require that sensitive data be shared. Institutions using LDAP as an authentication method must establish a different integration method to facilitate the transfer of data to Concourse. Send a message to
support@campusconcourse.com to request assistance establishing a new SSO integration.
Best Practices and Recommendations
If your institution currently authenticates users via LDAP, we recommend that you examine the existing integration and make it inaccessible to users before establishing a new SSO integration via SAML, CAS, or Shibboleth. It is also recommended that you consider alternative access points, such as LMS integration. To learn more about LMS integration as an alternative to LDAP authentication, check out our LMS Integration help article and email
support@campusconcourse.com with any questions.