We're working on connecting a Unity-based VR training application to Docebo (Axcelis University) so that the VR application can send xAPI statements and track learner completion data. We're currently stuck on the authentication/configuration portion of the integration and would appreciate any suggestions from others who have implemented something similar.
What We've Confirmed
- The Unity application appears to be successfully generating and attempting to send xAPI statements.
- Communication is reaching the Docebo environment, but authentication is failing.
- The error being returned is:
unauthorized_client- "The grant type is unauthorized for this client_id"
- The OAuth application is involved
What We've Tried
- Reviewed the Unity-side OAuth configuration.
- Attempted to connect using multiple Docebo URLs and connection settings.
- Created and tested a Docebo Connect recipe.
- Verified that the connector was originally intended to support external content/API integrations.
- Investigated whether the issue is related to OAuth grant type configuration versus client credentials setup.
Current Questions
- Has anyone successfully connected a Unity VR application directly to Docebo using xAPI?
- Are there specific OAuth grant types that must be enabled for Unity-to-Docebo communication?
- Should Unity be authenticating through a standard OAuth client, Docebo Connect, or another mechanism entirely?
- Are there any common configuration steps or permissions that are often missed when setting up this type of integration?
- Has anyone used Docebo as the endpoint for VR/xAPI content tracking and can share their architecture or best practices?
Any guidance, examples, documentation, or lessons learned would be greatly appreciated. We're trying to determine whether this is primarily an OAuth configuration issue, a credential exchange issue, or if we're approaching the integration incorrectly.
Thanks in advance!