Edlink supports integration with any authentication provider that uses OAuth 2.0.
Edlink integrates with any OAuth 2.0-compliant authentication provider to support Single Sign-On (SSO). OAuth 2.0 is used only for authentication and must be paired with a primary source for rostering. The email addresses or usernames provided by the OAuth 2.0 source must match those in the primary source for successful authentication.
Keep in mind, OAuth is a specification. It is not a provider directly. Another provider will implement OAuth, and we will connect with them.
Single Sign-On (SSO)
Edlink supports Single Sign-On (SSO) through an external OAuth 2.0-enabled authentication provider, allowing people to authenticate seamlessly into platforms connected to Edlink.
Secondary Source Only
OAuth 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 OAuth 2.0 provider to function correctly, the email addresses or usernames provided by the OAuth 2.0 source must match those in the primary source. If these identifiers do not align, people will not be able to authenticate successfully.
Rostering
Any OAuth 2.0 integration does not support rostering. 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
OAuth 2.0 does not support managing coursework or grade passback. It is strictly for SSO.