Brightspace connection messages

Data connection (OAuth 2.0)

Brightspace connection needs attention

Shown on Integrations > Brightspace and Billing when the LMS Account count has not updated for two or more days. The last count keeps its As of date until the connection works again. Rowseta checks this count daily through the Brightspace connection. Check the OAuth 2.0 connection and credentials below, then allow the next daily count check to run. This check is separate from a data sync and does not add an entry to sync history.

Brightspace URL must look like https://big-brain.brightspace.example.

The app may show Enter a Brightspace URL like followed by an example. For this demo, use https://big-brain.brightspace.example.

Cause: The address is missing https:// or a host name. Fix: Enter the main address of your Brightspace, starting with https://, without a page path.

Did you mean a different Brightspace address?

Cause: You pasted an address with a page path, such as /d2l/home. Fix: Select the suggested address.

Connection failed

The connection test gives a specific reason. It may say:

• The Brightspace OAuth 2.0 app is missing the datasets:bds:read scope. Check its scopes in Brightspace.
• Brightspace rejected the Client ID or app credentials. Check the OAuth 2.0 app in Brightspace.
• Rowseta could not reach Brightspace. Check the Brightspace address and try again.
• Brightspace issued a token but refused the data request. Check the Service User’s data access.
• Rowseta could not verify the Brightspace connection. Try again or contact support.

Cause: The connection test could not complete. Fix: Follow the specific reason. In Brightspace, check that the OAuth 2.0 app:

1. uses the Client Credentials grant type,
2. has the JWKS URL exactly as Rowseta shows it (your Rowseta address followed by /.well-known/jwks.json),
3. has the scope datasets:bds:read,
4. has a service user with Can Access Brightspace Data Sets,

and that the Client ID in Rowseta matches the app. Then select Test connection again.

Endpoint and client_id are required

Fix: Fill in both Brightspace URL and Client ID.

Failed to save credentials / Submission failed

Fix: Select the save button again. If a reason is shown, fix it first.

Failed to remove credentials

Fix: Reload the page and try again.

Connection not confirmed

Full message: Credentials were saved, but Brightspace is not connected yet. Return to step 1 and try again.

Fix: Select Update connection settings, test the connection, and save again.

OAuth 2.0 not connected

Fix: Follow Connect Brightspace.

Rowseta currently supports Brightspace by D2L only.

Cause: Rowseta works with Brightspace only. Fix: Leave your email in the form to hear when your LMS is supported.

LTI registration

Failed to generate setup link / Failed to revoke setup link

Fix: Try again. If it keeps failing, contact support.

This setup link is active, but the raw URL is not available in this browser session.

Cause: The link is shown only once, when it is created. Fix: Select Generate new link and copy it straight away.

Generating a new setup link will stop the existing link from working. Continue?

Fix: Confirm, and use only the new link in Brightspace.

Setup link expired on …

Also shown as invalid or expired setup link in the Brightspace registration window.

Cause: The link was not used before it expired, was revoked, or was replaced. Fix: Select Generate new link and register again with the new link.

missing setup_token parameter / missing openid_configuration parameter

Cause: The link was changed when pasted, or registration was not started from Brightspace’s Register Tool > Dynamic. Fix: Copy the whole setup link again and paste it in Register Tool > Dynamic.

failed to fetch platform configuration / invalid platform configuration / the platform configuration URL is not allowed

Cause: Rowseta could not read your Brightspace’s registration details. Fix: Try again. If it keeps failing, use standard registration.

platform does not support dynamic registration

Fix: Use standard registration.

Unsupported LMS Platform

Cause: The registration did not come from Brightspace. Fix: Rowseta supports Brightspace only.

registration request to platform failed / platform rejected registration

Also: failed to read registration response, registration failed: no client_id returned.

Cause: Brightspace refused to complete the registration. Fix: Check that your Brightspace account can register LTI Advantage tools, then generate a new link and try again.

Registration received

Full message: Rowseta received the Brightspace registration and needs to verify the Brightspace keyset before activation. Rowseta also emails its administrators LTI registration needs verification.

Fix: Open Integrations > LTI placements, select Verify connection, then Activate this platform. See If the registration was staged.

Verification failed: …

The reason can be, for example, JWKS fetch returned … or JWKS contains no RSA signing keys. Also shown as Failed to verify staged registration.

Cause: Rowseta still cannot read Brightspace’s signing keys. Fix: In Brightspace, check the registration is Enabled and its details are correct, then select Verify connection again.

Verify connection within the last 5 minutes before activating.

Also shown as verify before activating or Not yet verified.

Fix: Select Verify connection, then Activate this platform within 5 minutes.

Failed to activate staged registration / Failed to discard staged registration

Fix: Verify again, then try again.

Activating will replace your current Brightspace connection at …

Cause: A registration is already active. Fix: Activate only if you mean to switch to the new registration. Otherwise select Discard.

Discard staged registration

Fix: Type the Brightspace platform name exactly to confirm. Brightspace must register again before a discarded registration can be activated.

Disconnect Brightspace? LTI launches stop working until you register again.

Fix: Confirm only if you want to stop every Brightspace launch. Register again to restore them.

Failed to disconnect Brightspace

Fix: Try again.

Failed to save / Failed to update / all fields are required

Also: client_id is required, deployment_id is required, no existing registration to update.

Cause: A standard registration value is missing or wrong. Fix: Copy each value again from Brightspace: Client ID, Brightspace Keyset URL, Deployment ID, Brightspace OAuth2 Access Token URL, OpenID Connect Authentication Endpoint and Issuer.

LTI not connected

Fix: Follow Register Rowseta for LTI launches.

Rowseta can’t see changes made in Brightspace.

Cause: Changes made on the Brightspace side (disabling the registration, editing the deployment) are not visible to Rowseta. Fix: If launches stop working, check the registration under Manage Extensibility first. See Fix launch problems.