CloudShare supports the Learning Tools Interoperability (LTI) specification, a cross-platform protocol that enables learning platforms (like your LMS) to securely communicate and share data with external platforms (like CloudShare). LTI facilitates key learning platform activities, such as single sign-on, role definition, contextual information sharing, secure data handling, real-time interactions, and more. The advantage of using LTI with your LMS is that it provides all of this functionality without the need for custom program code or dedicated APIs.
By supporting LTI, CloudShare allows you to offer all of our advanced virtual lab features to your instructors and participants by accessing directly from your LMS.
Supported LTI Versions
CloudShare supports LTI 1.1 and LTI 1.3.
How CloudShare Works with LTI
When working with LTI, your LMS is referred to as the LTI Platform, and CloudShare is the LTI Tool.
When launching a virtual lab, it is crucial to ensure that your LMS sends the launching user's name and email address to CloudShare through the LTI request. This allows for seamless user identification and authentication within the virtual environment.
When integrating CloudShare with an LMS, a CloudShare virtual lab cannot be hosted within an iFrame. To ensure optimal functionality, make sure the host browser is opened in full-screen mode. This ensures a smooth and uninterrupted user experience during sessions.
CloudShare maps the LTI variables to standard integration fields:
- Content URL: This is the URL of the CloudShare content (i.e., the experience) that will be accessed from the LMS module. CloudShare maps this to a field called LTI Launch URL.
- LTI Client Key: This is CloudShare's unique LTI Toolaccount ID, allowing the LTI Platform (LMS) to identify CloudShare as the owner of the virtual lab. CloudShare maps this to a field called LTI Key.
- LTI Client Secret: This password authenticates CloudShare as the LTI Tool account. CloudShare maps this to a field called LTI Secret.
Limitations
Experiences deleted in CloudShare will still appear in the LMS and must be manually deleted there and vice versa.