Skip to content
Customer Support Portal
  • There are no suggestions because the search field is empty.

Why do I get an error while trying to authorize TidyUP or UDOIT in Cidiscape or ReadyGO?

A few errors may occur while authorizing TidyUP or UDOIT for Cidiscape or ReadyGO.

OAuth Error from the Cidiscape or ReadyGO LTI

If you authorize from the Cidiscape LTI and get an OAuth error, this is due to a Canvas SSO issue.

If you get an OAuth Error while authorizing Cidiscape or ReadyGO, see Why do I get an OAuth Error while trying to authorize the Task Runner in the Cidiscape or ReadyGO LTI?

For UDOIT, first try authorizing UDOIT while masquerading as the Task Runner. To do this:

  1. Masquerade as the Task Runner User
  2. Open UDOIT in a course or UDOIT Admin at the account level
  3. Select Connect
  4. Select Authorize
  5. Now, try to authorize the Task Runner for UDOIT in Cidiscape

Oops! An Error Occurred

This is usually due to a browser issue. For more information on resolving the Oops! An Error Occurred, see How do I resolve the error, "Oops! An Error Occurred" in the Cidiscape LTI?

Redirect Error

If you get the following redirect error, it means that your institution has set up custom developer keys for TidyUP or UDOIT. This causes an error with the authorization process because they are missing the redirect URI needed by Cidiscape or ReadyGO.

{"error":"invalid_request","error_description":"redirect_uri does not match client settings"}

If you get the error, no code was returned from the LMS for either TidyUP or UDOIT. This means your institution needs to move to use the tool's inherited developer key or add the redirect URI to the custom developer key.

Option 1: use TidyUP's inherited developer key (recommended)

If your institution would like to switch from a custom key to an inherited key, Cidi Labs has to update it on our side in order for it to work. To switch the developer key in our database contact support@cidilabs.com with your Canvas domain.

After we switch the developer key in our database, the following will occur:

  • Current users will be asked to re-authenticate TidyUP when their API tokens expire
  • All new users will authorize API tokens against the new developer key
  • Cidiscape task runner authentication should now work for TidyUP

Option 2: update the existing custom developer key

An alternative option is to update the existing custom developer key with the new redirect URI. This, however, is not recommended. Your institution can add the following redirect URIs to the custom developer key.

The new redirect URI for TidyUP is

https://cidiscape.ciditools.com/task-runner/authorize/check/tidyup

The new redirect URI for UDOIT is

https://cidiscape.ciditools.com/task-runner/authorize/check/udoit

If you continue to experience any errors while authorizing the Task Runner for Cidiscape, ReadyGO, TidyUP, or UDOIT, please submit a ticket to our support team by filling out the Cidi Labs Support Form.