Creating a new learning tool starts with an LTI Advantage administrator registering a new tool. Registering an LTI tool requires an administrator to either use the Dynamic Registration workflow (if available by the tool) or the manual workflow where the tool provides core details, such as the tool domain URL, tool redirect URL or keyset URL.

For any tool to create links, it needs to first be registered. Disabled registrations do not allow users to perform launches or use the tool. When setting up a new tool, D2L recommends that you disable it during setup. This allows administrators to create links and configure the tool fully before enabling it.

The required fields in the UI come directly from your tool. It is possible for tools to provide many redirect URLs. To add more, click + Add Redirect URL . The Domain URL is used in Brightspace to assist with domain matching, allowing Brightspace to suggest tools to bind ad-hoc links to during creation. You only need the Keyset URL if you use the extensions.

Substitution and custom parameters can be created at the registration level and cascade down to the deployment and link levels.

Once a tool is registered, you receive a Client Id, Brightspace Keyset URL, and a Brightspace OAuth2 Access Token URL to provide to the tool.

  • Domain: Used for domain matching only (when creating new links through content to populate the dropdown) .
  • Redirect URLs: Redirect URLs which are end points where the authorization response can be sent to. This can be one or many values.
  • OpenId Connect Login URL: The OpenId URL of the tool that is the location where the tool will launch to during the initial OIDC launch.
  • Target Link URI: If a tool does not return a URL for the LTI link (ltiResourceLink) in the Deep Linking response, the target link URI is used as the URL. If neither are supplied, the domain in the LTI Registration is used.
  • Keyset URL: The URL where the tool stores the keys. Used as a reference point when D2L performs a key lookup during the OIDC launch.