Return to Domain_Configuration_LTI_Tools.tex CVS log

Up to [LON-CAPA] / loncom / html / adm / help / tex

Annotation of loncom/html/adm/help/tex/Domain_Configuration_LTI_Tools.tex, revision 1.4

1.1       raeburn     1: \label{Domain_Configuration_LTI_Tools}
                      2: 
                      3: By adding one or more External Tools to a domain, you will be enabling use of your LON-CAPA domain as an LTI Consumer (where LTI = Learning Tool Interoperability). Under the LTI protocol, the user's identity, as well as the course context, can be sent to the external tool (the Provider) which will trust the identity and role information provided by LON-CAPA (the Consumer). Any LON-CAPA data being provided are included in an encrypted form in the tool launch page sent to the user's web browser by LON-CAPA. The external tool will assign appropriate privileges to the user within the tool, based on the user's role.  
                      4: 
                      5: The shared key and secret used to encrypt data sent to the Tool Provider are typically provided to you when contact the Provider to let them know you would like to use their tool with your Learning Management System, i.e., with the LON-CAPA service for your domain.
                      6: 
                      7: When a Domain Coordinator includes ``External Tools (LTI)'' as one of the domain settings to display/modify via the ``Set domain configuration'' link in the Main Menu, a table will be displayed listing all currently available External Tools (i.e., LTI Providers) configured for use in the domain, as well as an ``Add'' checkbox (for the last row in the table), used to add a new External Tool.
                      8: 
                      9: Internally in LON-CAPA each external tool you configure for your domain receives a unique numerical ID (starting at 1), which remains unchanged, regardless of any future changes made to the configuration for that particular tool.  A drop-down list in the left column of the External Tools table can be used to change the order in which available tools are listed in both the domain configuration table, and in the dropdown list in the ``External Tool Editor'' item available in the Course Editor (``External tab''), when one or more tools are available in the course's domain.
                     10: 
                     11: Settings available for each External Tool in the domain are as follows:
                     12: 
                     13: \begin{itemize}
                     14: 
                     15: \item{\textbf{Required settings}}
                     16: 
                     17: The Provider name will be the Tool name shown in the listing of available External Tools in the Course Editor.
                     18: 
                     19: Keys and secrets for LTI Tools, which should be specific to a LON-CAPA domain, are stored internally in a separate GDBM file from the other domain configuration information in your domain. For each LTI Tool, the unique key and secret will be provided to you by the Tool Provider, as will the remote URL which will handle LTI launch requests from link(s) to instance(s) of the tool in LON-CAPA courses in your domain.
                     20: 
                     21: Each LTI tool can be configured to allow additional information to be appended to the Tool URL for each tool instance by a Course Coordinator.  There are four other required settings: Version, Message Type, Signature Method and Nonce lifetime. You will likely use the default values provided for each of the four. 
                     22: 
                     23: \item{\textbf{Optional settings}}
                     24: 
                     25: There are five optional settings, for which you can set default values, which optionally you may allow a Course Coordinator to override for each tool instance: Display target (iFrame, Tab, or Window), Width and Height (if target is Window), default link text, and default explanation. 
                     26: 
1.3       raeburn    27: Optionally, you can also:
                     28: \begin{itemize}
                     29: \item Set whether a tool can return grade information to the LON-CAPA course from which it was launched, for the user (and tool instance).  You can also set the lifetime (in days) of the unique grade passback ID sent to the external tool, each time a user launches a particular instance of a tool in a course.
                     30: \item Set whether a tool can retrieve roster information for the LON-CAPA course from which it was launched, within a specified number of seconds from launch.
                     31: \item Upload a small image file, which will be used as an icon for the file type for each tool instance in the Course Editor.
                     32: \end{itemize}
                     33: 
1.1       raeburn    34: \item{\textbf{User data sent on launch}}
                     35: 
1.4     ! raeburn    36: For each External Tool, you will set what data are sent when it is launched. You can choose to send any or all of: Full Name, First Name, Last Name, E-mail address, Role (i.e., current ``LTI'' role, as determined from current role in LON-CAPA), and User (either username or username:domain) for the user launching a tool instance in a course. 
1.1       raeburn    37: 
                     38: \item{\textbf{Role mapping}}
                     39: 
                     40: LTI uses a more restricted set of roles - Instructor, Content Developer, Teaching Assistant or Learner - than are available in LON-CAPA.
                     41: 
                     42: For each tool you will set mapping to an LTI role to be used for each standard LON-CAPA role. At a minimum you should likely set that Course Coordinator (LON-CAPA) will map to Instructor (LTI), and Student (LON-CAPA) will map to Learner (LTI). 
                     43: 
                     44: \item{\textbf{Configurable in course}}
                     45: 
                     46: The five optional settings: display target (and width and height, when target is window), default link text, and default explanation can be set to be configurable for each instance of a tool in a course by the Course Coordinator.
                     47: 
1.4     ! raeburn    48: In addition, two other items sent on launch to the external tool - Course label and Course title - can be set to be configurable by a Course Coordinator. If Course label is not configurable, the institutional course code for the LON-CAPA course will be used, whereas if Course title is not configurable, the LON-CAPA course title will be used, respectively, for context\_label and context\_title, as part of the data sent to the external tool on launch.
1.1       raeburn    49: 
                     50: Lastly, the Provider URL can be set to be configurable, so that a Course Coordinator can specify text (potentially unique for each tool instance), such as a path or query string, which will be appended to the default Provider URL to which the encrypted LTI data are sent on launch.
                     51: 
                     52: \item{\textbf{Custom items sent on launch}}
                     53: 
                     54: Besides the set of standard LTI items, you may also add name=value pairs to send additional data to the LTI Provider on launch of the tool in a LON-CAPA course.
                     55: 
1.4     ! raeburn    56: LON-CAPA will automatically prepend \emph{custom\_} to the name of each custom item you set in the tool configuration when preparing the data to send to the external tool.
1.1       raeburn    57: 
1.4     ! raeburn    58: If the entry in the \emph{value} textbox is of the form: LONCAPA::env\{lcenvkey\}, where \emph{lcenvkey} is the name of an item in LON-CAPA's own \%env hash, then the LONCAPA::env\{lcenvkey\} value in the custom\_name=value pair sent on launch will be the value of \$env\{lcenvkey\} in effect in the user's LON-CAPA session. Otherwise, whatever value is set in the domain configuration for the tool for item \emph{name} will be sent as the pair: custom\_name=value.
1.1       raeburn    59: 
                     60: \end{itemize}
                     61: 
1.4     ! raeburn    62: For reference the complete set of parameters (other than custom\_*) which could be present in the data POSTed on LTI launch (depending on how the tool is configured) is as follows:
1.1       raeburn    63: 
                     64: \begin{verbatim}
                     65: 
                     66: basiclti_submit
                     67: context_id
                     68: context_label
                     69: context_title
                     70: context_type
                     71: ext_ims_lis_basic_outcome_url
                     72: ext_ims_lis_memberships_url
                     73: ext_ims_lis_memberships_id
                     74: launch_presentation_document_target
                     75: launch_presentation_locale
                     76: launch_presentation_height
                     77: launch_presentation_width
                     78: lis_outcome_service_url
                     79: lis_person_contact_email_primary
                     80: lis_person_name_family
                     81: lis_person_name_full
                     82: lis_person_name_given
                     83: lis_person_sourcedid
                     84: lis_result_sourcedid
                     85: lti_message_type
                     86: lti_version
                     87: oauth_consumer_key
                     88: oauth_nonce
                     89: oauth_signature
                     90: oauth_signature_method
                     91: oauth_timestamp
                     92: oauth_version
                     93: resource_link_id
                     94: resource_link_title
                     95: roles
                     96: tool_consumer_info_product_family_code
                     97: tool_consumer_info_version
                     98: tool_consumer_instance_description
                     99: tool_consumer_instance_guid
                    100: tool_consumer_instance_name
                    101: tool_consumer_instance_url
                    102: user_id
                    103: 
                    104: \end{verbatim}