EchoVideo

Need help using EchoVideo? Email support@echo360.com
Include SSOID or SISID in LTI launches when provisioning User accounts in EchoVideo
As an Admin and Identity Manager for our institution, I would like LTI payloads/launches from Canvas to Echo360 to include an SSOID and/or externalId for users and update their account with that information. With this workflow, we would not have to identify which Echo360 user accounts do not have an SSOID or externalId and then update in a daily scheduled job via Echo360 API calls (or sometimes manually, individually or in bulk from imports/exports). It would uniquely identify the account owner by matching Echo360 accounts with university IDs. Email addresses such as John.Smith@colostate.edu are not unique identifiers since addresses of former users can be reused by new users with the same first and last name. Based on Canvas currently acceptable LTI parameters, the closest available parameters may be these: $Canvas.user.sisid — User’s SIS ID - This should populate the externalId field, which we currently do via Echo360 API calls. This is our university's 9-digit ID number (CSU ID) which uniquely identifies the user. It cannot be seen or edited in the Echo360 UI, but would be helpful to populate this to associate with the correct person. $Canvas.user.login_id — User’s login/username - This is our university's NetID for about 98% of users who log in with SSO via Shibboleth/SAML. (Non-credit users and admins log in with a Canvas username and password.) We currently use Echo360 API calls to populate SSOID in Echo360 with our university's NetID appended with our university's domain (@ colostate.edu ), which is the eduPersonPrincipalName attribute in the eduPerson LDAP schema.
1
·

considering

Load More