[Building Sakai] Fwd: LTI Tool Consumer certification test results (ref: 9c4b2b44-fd14-442f-9962-6f1f71163848)

[Adrian Fish]

Superb. Nice work.


On 14 February 2014 04:43, Charles Severance <csev at umich.edu> wrote:

> Hi all,
>
> I just wanted to share that (a) IMS LTI 2.0 is final, and (b) Sakai-10 is
> the first officially certified LTI 2.0 Tool Consumer.
>
> /Chuck
>
> Begin forwarded message:
>
> *From: *Charles Severance <csev at umich.edu>
> *Subject: **LTI Tool Consumer certification test results (ref:
> 9c4b2b44-fd14-442f-9962-6f1f71163848)*
> *Date: *February 12, 2014 at 3:02:28 PM EST
> *To: *IMS LTI Certification submission <svickers at imsglobal.org>
> *Cc: *Charles Severance <csev at umich.edu>
>
> Tests for: Sakai-10 (Alpha)
>
> Ref: 9c4b2b44-fd14-442f-9962-6f1f71163848 for University of Michigan
>
> I am submitting my results from the certification tests for your approval.
>
> I have passed the certification tests for the following releases of LTI
> and wish to apply for certification:
>
>    1. 2.0
>    2. Outcomes
>
> *Other comments:*
>
> Awesome technical support!
>
>
> Confirmation statement
>
> I confirm that the test results generated are an accurate representation
> of a properly executed certification testing process. I also confirm that I
> am familiar with the LTI specification and I am not aware of any
> circumstances when my application would fail the tests undertaken or fail
> to comply with any untested requirements of the specification.
> Test resultsTestRequired forStatus*1: Tool Registration* 1.1: The
> contents of the registration request are valid2.0Pass1.2: Invalid tool
> proxy is rejected2.0Pass1.3: Valid tool proxy is accepted2.0Pass*2:
> Protocol Compliance and Resource Information* 2.1: All launch messages
> have required parameters1.0, 1.1, 1.1.1, 1.2, 2.0Pass2.2: Sends
> resource_link_title1.0, 1.1, 1.1.1, 1.2Pass2.3: Sends
> resource_link_description1.0, 1.1, 1.1.1, 1.2OK2.4: Sends
> tool_consumer_info_product_family_code1.1, 1.1.1, 1.2Pass2.5: Sends
> tool_consumer_info_version1.1, 1.1.1, 1.2Pass2.6: All messages have a
> recognised message type1.0, 1.1, 1.1.1, 1.2, 2.0Pass*3: OAuth and Signing
> Requests* 3.1: Sign with agreed consumer key and secret1.0, 1.1, 1.1.1,
> 1.2, 2.0Pass3.2: Can sign requests with URL parameters1.0, 1.1, 1.1.1,
> 1.2, 2.0Pass3.3: Can sign a request with a URL parameter with space in
> the value parameter1.0, 1.1, 1.1.1, 1.2, 2.0Pass3.4: Must include
> oauth_callback for OAuth 1.0A compliance1.0, 1.1, 1.1.1, 1.2, 2.0Pass3.5:
> Parameters are encoded using UTF-81.0, 1.1, 1.1.1, 1.2, 2.0Pass*4: Custom
> Field Support* 4.1: Can send custom fields1.0, 1.1, 1.1.1, 1.2Pass4.2:
> Properly maps special characters and case in custom fields1.0, 1.1,
> 1.1.1, 1.2ToDo4.3: Supports $User.id substitution variable1.2Pass4.4:
> Supports $User.username substitution variable1.2Pass4.5: Supports
> $ToolConsumerProfile.url substitution variable1.2, 2.0Pass4.6: Supports
> Tool Settings substitution variables2.0Pass*5: User Information* 5.1:
> Sends a user_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass5.2: Sends Learner role1.0,
> 1.1, 1.1.1, 1.2, 2.0Pass5.3: Sends Instructor role1.0, 1.1, 1.1.1, 1.2,
> 2.0Pass5.4: Follows role naming rules1.0, 1.1, 1.1.1, 1.2, 2.0Pass5.5:
> Sends request with a valid name and email for the user1.0, 1.1, 1.1.1,
> 1.2, 2.0Pass5.6: Sends request with only lis_person_contact_email_primary
> but no name information1.0, 1.1, 1.1.1, 1.2ToDo5.7: Sends valid user name
> information but no email address1.0, 1.1, 1.1.1, 1.2ToDo5.8: Can suppress
> all identifiable user information1.0, 1.1, 1.1.1, 1.2ToDo5.9: Send a
> lis_person_sourcedid1.0, 1.1, 1.1.1Pass5.10: Send a role_scope_mentor1.1.1,
> 1.2ToDo5.11: Send a lis_person_sourcedid1.2Pass*6: Context support* 6.1:
> Can send a context_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass6.2: Can send a
> context_label1.0, 1.1, 1.1.1, 1.2Pass6.3: Can send a context_title1.0,
> 1.1, 1.1.1, 1.2Pass6.4: Can send a request without a context_id1.0, 1.1,
> 1.1.1, 1.2, 2.0OK6.5: Can send a context_type1.0, 1.1, 1.1.1, 1.2, 2.0OK6.6:
> Follows context_type rules1.0, 1.1, 1.1.1, 1.2, 2.0Pass6.7: Send a
> lis_course_offering_sourcedid1.0, 1.1, 1.1.1, 1.2OK6.8: Send a
> lis_course_section_sourcedid1.0, 1.1, 1.1.1OK6.9: Send a
> lis_course_section_sourcedid1.2ToDo*7: Consumer support* 7.1: Can send a
> tool_consumer_instance_guid1.0, 1.1, 1.1.1, 1.2, 2.0Pass7.2: Can send a
> tool_consumer_instance_name1.0, 1.1, 1.1.1, 1.2, 2.0Pass7.3: Can send a
> tool_consumer_instance_description1.0, 1.1, 1.1.1, 1.2, 2.0Pass7.4: Can
> send a tool_consumer_instance_contact_email1.0, 1.1, 1.1.1, 1.2, 2.0OK*8:
> Multiple Requests and Consistency* 8.1: Send message from a second
> resource_link_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass8.2: Sends a different
> user_id1.0, 1.1, 1.1.1, 1.2, 2.0Pass8.3: Can send a different context_id1.0,
> 1.1, 1.1.1, 1.2, 2.0Pass8.4: Can send multiple resource_link_id values
> with the same context_id1.0, 1.1, 1.1.1, 1.2, 2.0OK8.5: A
> resource_link_id never moves from one context_id to another1.0, 1.1,
> 1.1.1, 1.2, 2.0Pass8.6: Consistency of context_id/user_id/role mappings1.0,
> 1.1, 1.1.1, 1.2, 2.0Pass*9: Launch Support* 9.1: Sends
> launch_presentation_locale parameter1.0, 1.1, 1.1.1, 1.2, 2.0Pass9.2:
> launch_presentation_document_target parameter is valid1.0, 1.1, 1.1.1,
> 1.2, 2.0OK9.3: launch_presentation_width parameter is valid1.0, 1.1,
> 1.1.1, 1.2, 2.0OK9.4: launch_presentation_height parameter is valid1.0,
> 1.1, 1.1.1, 1.2, 2.0OK9.5: launch_presentation_css_url parameter is valid1.0,
> 1.1, 1.1.1, 1.2, 2.0Pass9.6: launch_presentation_return_url parameter is
> valid1.2, 2.0Pass*10: Support for Outcomes Service* 10.1: Sends
> lis_result_sourcedid and lis_outcome_service_url parameter1.1, 1.1.1,
> OutcomesPass10.2: Outcomes Service supports replaceResult operation1.1,
> 1.1.1, OutcomesPass10.3: Outcomes Service supports readResult operation
> and returns the proper value1.1, 1.1.1, OutcomesPass10.4: Outcomes
> Service supports deleteResult operation1.1, 1.1.1, OutcomesPass10.5:
> Result is properly deleted after deleteResult operation1.1, 1.1.1,
> OutcomesPass10.6: Outcomes Service properly handles unsupported operations1.1,
> 1.1.1, OutcomesPass10.7: replaceResult does not accept out of range values1.1,
> 1.1.1, OutcomesPass10.8: replaceResult accepts values of 0 and 11.1,
> 1.1.1, OutcomesPass10.9: replaceResult does not accept invalid values1.1,
> 1.1.1, OutcomesPass10.10: lis_outcome_service_url passed for all roles1.1,
> 1.1.1, OutcomesPass10.11: Outcomes Service rejects invalid replaceResult
> requestOutcomesPass10.12: Outcomes Service rejects invalid readResult
> requestOutcomesPass10.13: Outcomes Service rejects invalid deleteResult
> requestOutcomesPass*11: Tool Consumer Profile* 11.1: URL does not change
> between launches1.2, 2.0Pass11.2: Format matches media type1.2, 2.0Pass11.3:
> Declares required capabilities1.2, 2.0Pass11.4: Property values are
> consistent with launch parameters1.2, 2.0Pass11.5: Required services are
> declared2.0Pass*12: Tool Settings* 12.1: Supports GET method2.0Pass12.2:
> Supports PUT method2.0Pass12.3: Supports PUT method using simple format2.0
> Pass12.4: Supports bubble=all option2.0Pass12.5: Supports bubble=distinct
> option2.0Pass12.6: Rejects multi-level PUT requests2.0Pass12.7: Rejects
> requests not properly signed2.0Pass
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20140214/0e5a1877/attachment.html