Description
We are an Idaho State Agency created to help support schools in online learning. We are looking for Zoom with LTI Pro to launch through our LMS directly to the Web Client as student Chromebooks have limited ability to load apps.
The current launch will authenticate to a client but will not authenticate to the web client or pass user credentials through to the web client.
Is there a way to launch the web client by default through the LTI launch, or to authenticate a web client launch?
Since the Web Client is not apart of the API Platform, your best bet is to reach out to our product team at support.zoom.us so they can further assist.
My understanding is that the current LTI Pro implementation doesn’t log users into zoom per se, but uses the credentials of the user who sets up the LTI to generate the page, which uses APIs to generate login tokens embedded in the zoom meeting links that will log in the user via the desktop client. The important bit is page is generated without the user being logged in, so if you open the LTI Pro frame in a new window you’ll see the url is https://applications.zoom.us/lti/rich and not https://[instance].zoom.us/meeting#/upcoming.
I believe options to actually log users into a zoom instance via the LTI and/or SSO (if the LMS and zoom instance share the same SSO IDP?) are on the roadmap.
Interesting, so when the user instead selects the web client then the web client isn’t accepting the tokens embedded in the meeting links because it is pushing them off to a new URL. It seems like that page where the launch is initiated could be modified to also include and pass on the token to the webclient for launch.
Does the web client even support token based launches?
