Data connection
Start at Integrations > Brightspace. For the first connection, follow Connect Brightspace. LTI launches use a separate registration.
Check the connection
Section titled “Check the connection”The OAuth 2.0 app registration card shows OAuth 2.0 connected or OAuth 2.0 not connected. Its disclosure says: During evaluation, Rowseta checks the LMS Account count daily through the Brightspace connection after the first completed sync. On an annual subscription, it checks only in the 21 days before the annual term ends.
If Brightspace connection needs attention appears, the detail says: The LMS Account count has not updated for 2 or more days. The last count keeps its date until the connection works again. Check the connection and credentials below. Count checks follow the timing above and are separate from a data sync.
Update the credentials
Section titled “Update the credentials”Use this for new OAuth 2.0 app credentials on the same Brightspace instance. An Organization is tied to one Brightspace instance. Changing the host is refused with This Organization is connected to {host}. Rowseta can’t switch an Organization to a different Brightspace. Contact support if this is wrong. Here, {host} is the connected Brightspace host. Contact support for a different Brightspace instance.
- Select Update credentials. Copy the JWKS URL and Scope (
datasets:bds:read) shown by Rowseta into the Brightspace app. The key location must match exactly. - Enter the Brightspace URL and the app’s Client ID. For example, the Brightspace address for Big Brain Energy College is
https://big-brain.desire2learn.com. This is an example address, not a required suffix. Enter the main address without a page path. - Select Test & save. Rowseta tests before saving; Connected confirms success.
For an Evaluation Organization with zero free syncs left and no completed sync, saving the Brightspace connection starts a price check automatically. It does not start a first sync. Follow the price check and purchase steps.
If the address has a page path, use the suggested main address. Correct an invalid address in the field before testing.
If the test fails, check the Brightspace app’s Client Credentials grant, datasets:bds:read scope, exact JWKS URL, and service user’s Can Access Brightspace Data Sets permission. Check that the Client ID matches, then test and save again. The failed sync dialog’s Open Brightspace connection action returns here.
If there is no connection yet, follow Connect Brightspace.
This data connection supports Brightspace only.
Remove the credentials
Section titled “Remove the credentials”Select Remove credentials. Syncs stop until you reconnect; already synced data remains.
If removal fails, reload the page and try again.