Viewer System Role Receives 404 Ally Token Error When Accessing Course Content That Uses Ally




 
Viewer System Role Receives 404 Ally Token Error When Accessing Course Content That Uses Ally

Date Published: Jul 11,2025 Category: Planned_First_Fix_Release:X3900_125_0_Release; Product:Blackboard_Learn_SaaS; Version:X3900_118_0,X3900_121_0,X3900_123_0   Article No.: 000090895

Producto: Learn SaaS

Versión: SaaS

Paquetes de servicio: 3900.118.0, 3900.121.0, 3900.123.0

Descripción:

When attempting to access course content that uses Ally, the newly system role 'Viewer' released in the in 3900.118 version, receives a 404 Ally token error. 

Pasos para repetir:

  1. Log into Blackboard Learn Ultra Experience as an administrator

  2. Create a user and assign them the Viewer system role

  3. Create two Ultra courses

  4. In Course 1, go to Create > Document, and add text as the content

  5. In Course 2, go to Create > Document, and upload a file (e.g., a PDF)

  6. Log in as the user with the Viewer system role

  7. Go to Course 1 and access the document

  8. Go to Course 2 and access the uploaded PDF file

Observed Behavior:

In Course 1, the "Ally token request API not found" error is shown in the document. Neither closing nor refreshing the page helps.

In Course 2, the Ally token request appears once on the course content page. If it is closed, you can continue navigating through the course. However, if the page is refreshed, the request reappears.

Expected Behavior:

Viewer System Role shouldn't encounter any issues with Ally.

 

 

 

 


Resolución/Solución alternativa:

Until the root cause is resolved, administrators may manually grant the necessary entitlement to the Viewer role by navigating to Course/Organisation > Access unavailable course. This will help prevent the error from occurring.



Versión de destino: SaaS-Fixed (v3900.125.0)