SSO with the IDP of the Customer
Edcast supports OAuth & SAML2.0 for the SSO with the IDP of the Customer.
Customers also have the option to additionally allow users to login using their User name & Password on the Edcast portal.
Edcast has successfully integrated with Microsoft Active Directory, Azure Active Directory , Ping Identity & One Login
SSO with the LMS / Content Provider
- where Edcast is the IDP
Edcast supports SSO with the LMS / Content Provider via SAML 2.0 only
- where the customer provides the IDP
In this scenario , the SSO is directly handled by the customer without involving Edcast
Edcast supports OAuth for the SSO with the IDP of the Customer.
Following attributes are to be shared with Edcast by the customer:
- Authorization endpoint
- Token endpoint
- JWKS endpoint
- Userinfo endpoint (optional)
To set up the IDP for testing the SSO connection, please download your metadata and send us your metadata XML file. We will then set up the portal on our side and send you a test link.
Make sure that your SAML request includes a unique and permanent NameID. This should ideally be an employee number or similar.
Email Id change scenarios make use of the SAML Name ID
Using the user's email address is not recommended as it might change (e.g. name change after marriage)
During the Integration with the Customer's IDP, Edcast SSO accepts the following attributes from the SAML Response:
- SAML Name ID (Default SSO attribute)
During the Integration with the LMS / Content Provider, Edcast SSO sends the following attributes from the SAML Response:
- SAML Name ID = email id / employee ID
If your company portal already has existing customer users that have self-registered, we will need to upload the NameID for all existing users to our database, in order to ensure they will continue having access to their account information.
- SAML Metadata XML file
Updated almost 3 years ago