Edlink supports integration with any authentication provider that uses OpenID Connect (OIDC).
Edlink integrates with any OIDC-compliant authentication provider to support Single Sign-On (SSO). OIDC is used only for authentication and must be paired with a primary source for rostering. The email addresses or usernames provided by the OIDC source must match those in the primary source for successful authentication.
Keep in mind, OIDC is a specification. It is not a provider directly. Another provider will implement OIDC, and we will connect with them.
Single Sign-On (SSO)
Edlink supports SSO through an external OIDC-enabled authentication provider, allowing people to authenticate seamlessly into platforms connected to Edlink. Edlink's support of OIDC applies to any authentication provider that complies with the OpenID Connect standard.
Secondary Source Only
OIDC is designed to be used exclusively as a secondary source within Edlink. This ensures that authentication is seamlessly layered on top of existing roster data from a primary source.
Email/Person Matching Required
For the OIDC-based SSO provider to function correctly, the email addresses or usernames provided by the OIDC source must match those in the primary source. If these identifiers do not align, people will not be able to authenticate successfully.
Rostering
Any OIDC integration does not support rostering capabilities. Person, class, and enrollment data must come from a primary source, such as an LMS, SIS, or other (CSV/SFTP) integration.
Managing Coursework and Grades
OIDC does not support managing coursework or grade passback. It is strictly for SSO.