Configuring LTI for TAO Authoring
LTI integration allows test authors to create items and tests using TAO Authoring as an embedded tool. This topic provides details on API parameters used to launch the TAO Authoring tool via LTI.
Launch URL
This parameter is required to connect TAO Authoring to LTI.
"https://{TAO_AUTHORING_URL}/taoLti/AuthoringTool/launch"
Message type
This parameter is used to generally define which type of entity you are linking in the configuration. Entering a value for this parameter is required by the LTI tool.
For more information, see Message Type claim in https://www.imsglobal.org/spec/lti/v1p3#message-type-claim.
Example:
"https://purl.imsglobal.org/spec/lti/claim/message_type": "LtiResourceLinkRequest"
Target link URI
This parameter is used to define TAO Authoring tool in the launch and must carry the same value as the launch URL. Entering a value for this parameter is required.
For more information, see Target Link URI in https://www.imsglobal.org/spec/lti/v1p3#target-link-uri.
Example:
"https://purl.imsglobal.org/spec/lti/claim/target_link_uri": "https://{TAO_AUTHORING_URL}/taoLti/AuthoringTool/launch"
Role
The roles
parameter is used to define the user as a test author (or content developer). Entering a value for this parameter is required.
For more information, see Roles claims in https://www.imsglobal.org/spec/lti/v1p3#roles-claim.
key | Value | Default | Description |
---|---|---|---|
|
|
| LTI role of the test author: “ContentDeveloper” LTI role of a developer: “Developer” |
User identity
These parameter is used to define the authoring tool users. Entering a value for this parameter is required to launch the TAO Authoring tool.
For more information, see User Identity claims in https://www.imsglobal.org/spec/lti/v1p3#user-identity-claims.
key | Value | Default | Description |
---|---|---|---|
|
|
| The User Identifier is unique to the platform from which the LTI launch occurs. A unique identifier must be entered for the content developer. This value cannot be left blank; test authors cannot be anonymous. |
Example:
"sub":"13242-1234657-65"