The current configuration can be downloaded to a file (which can then be uploaded at a later time), or backed up and restored to/from the server. The download and backup options are only available when any changes made have been saved.
Select a file to upload; this must be a file which was previously downloaded from this system.
Alternatively, the Test Tool can be opened using LTI 1.3 credentials or directly in a browser and the Platform's credentials and service endpoints entered manually via the Security Model and Service sections. The tool also supports the LTI 1.3 automated registration process (as currently implemented by Moodle).
Use this menu to change the page which is displayed.
This tab summarises the message received which opened the system.
This tab displays the credentials and security profile used for connections with the Platform. These values are used when sending service requests to the Platform. Changing them allows invalid requests to be tested. For LTI 1.3 connections, the tab also displays the configuration details for the tool; the public keyset URL or public key should be shared with the platform. The details shared by the platform should be configured on this tab as well.
If a profile has been obtained from the platform it will be also be displayed on this tab.
This tab is displayed for ContentItemSelectionRequest or LtiDeepLinkingRequest messages. You can use it to select sample content-item(s) to be returned to the Platform, or to create a bespoke item. Messages to be returned with the items can also be added.
This menu lists all the services supported by the Test Tool. Selecting a service from the menu will display the settings relevant to its use, including the endpoint(s). The settings page can be used to send requests to the Platform; use the View last service request button to inspect the last request made and response received. When using LTI 1.3, the OAuth 2 Access Token service should be used first to obtain an access token for the required service scopes.
This system uses sessions to manage your activity; these sessions last for at least 2 hours. However, when a new session is started some endpoints may change and so any existing integrations you are testing may require updating. Signing into the system using a Google ID allows you to have a static set of endpoints to avoid this issue. It also provides the following options:
The only data shared by this process is your email address and your ID number as supplied by Google.
To aid the re-use of an LTI 1.3 platform, it is possible to save a configuration and have it associated with your Google ID. By default each Google ID can have up to 10 saved platform configurations (use the Feedback option on the Help to enquire about increasing this limit if it is not sufficient for your needs).
To save a configuration, just enter its details into the fields on the Security Profile page and click on the Save button in the header of the Platform Details section. If a platform with the same Platform ID, Client ID and Deployment ID is already defined, its details will be updated with the new values.
The Registered platforms button opens a list of all the existing configurations which have been saved; full details can be displayed by clicking on the plus sign at the start of the row. Initially a configuration is given a name of Unnamed; click on the name to change it. A configuration can be made available for use by other users by turning on its Public setting. Click on the download icon in the Action column to copy the configuration settings to the Security Profile page. (A configuration can also be copied by selecting its name from the drop-down list on the Registered platforms button.) Click on the delete button to remove the configuration.