Edlink's support for OAuth 2.0 and OIDC ensures that integrating with HelloID is straightforward, allowing features like Single Sign-On (SSO) and token-based resource access.
Requirements for Integration
For successful integration between HelloID and Edlink, specific technical requirements must be met.
Prerequisites
- A primary data source (SIS, LMS, or CSV upload) must be configured before HelloID integration.
- HelloID is used exclusively for authentication, not roster data management.
- Valid HelloID subscription with OAuth 2.0 and OIDC capabilities enabled.
- HelloID users are required to have an email address associated with their account.
Data Alignment
- Email Matching: User email addresses in HelloID must match those in your primary data source.
- Identity Verification: HelloID handles user authentication while roster data comes from your primary source.
Implementation Notes
- Authentication Only: HelloID serves as a secondary authentication layer.
- Data Source Requirements: Primary roster data must come from another source.
- Protocol Support: Integration relies on standard OAuth 2.0 and OIDC protocols.
For technical assistance with HelloID integration, contact Edlink support.