Using custom developer keys for TidyUP or UDOIT causes an error with the authorization process because they are missing the redirect URI needed by Cidiscape.
If you get the error Authentication problem, 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.
Solution
There are two options for the institution to fix this issue.
Option 1
The institution should use TidyUP's inherited developer key.
If your institution would like to switch from a custom key to an inherited key, Cidi Labs has to update on our side in order for it to work. To switch the developer key in our database contact support@cidilabs.com.
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
An alternative option is to update the existing custom developer key with the new redirect URI. This, however, is not recommended.
The 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