• Type: Sub-task
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0
    • Fix Version/s: 10.0
    • Component/s: Kernel
    • Labels:


      Use the LRS API and create an implementation which is compatible with tincanapi compatible servers

      Goal is to create an internal integration with the experience API ( which is suitable for inclusion in the Sakai trunk and future releases. The integration will focus on using core aspects of Sakai like the events system and flexible industry tech such as AOP to allow for a high level of data capture. Must support Basic Auth API authentication or OAuth (rfc5849) security (with HMAC-SHA1) and SSL for statement requests.
      On startup, the Sakai servers will verify they can connect to the LRS (probably using the activities/state portion of the API). If they cannot connect then they will register error messages in the log and IDEALLY notify a system admin via email. Also, all incoming activity statements will be logged out with a warning while the LRS cannot connect (this may not be desirable).

      The provider should handle checking it's configuration values (lrs.tincanapi....) for:
      A) API URL
      B) Security parameters (consumer key, secret, username:password, etc.)
      C) Version of the API (support for 0.95 or the most current version at time of development)

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  aaronz Aaron Zeckoski (Inactive)
         Alan Berg
                • Votes:
                  0 Vote for this issue
                  2 Start watching this issue


                  • Created:

                    Git Source Code