trial.brightspace.com LTI not support Grade

[Ebinezar Prawin]

Hi All,

I have integrated the LTI with D2L at trial.brightspace.com. When I'm accessing the LTI app, I can get the list_outcome_service_url and lis_result_sourcedid.  But the problem is, when I send back the grade with the list_outcome_service_url, it's saying unsupportedLISoperation.

I have did the same thing on Moodle, Canvas and Blackboard. Everything working perfect. Please help me to solve this issue.

[Desire2Learn Staff: Sarah-Beth]

Hi Ebinezar

I notice that you're referring to the "LIST_outcome_service_url" rather than the "LIS_outcome_service_url". Is that just a typo in this forum post, or are you referencing the parameter that way in your code?

A few things to check

• In your LMS Logs, are you getting "Error while deserializing request xml" - if so, this suggests that the request was badly formed and couldn't be handled
  
• If the request is getting de-serialized properly, there's still a chance that the body has bad data in it that can't be handled - i.e. it contains data that is not properly formatted for the tool consumer

Can you inspect the body to verify that it's well-formed. If you'd like an extra set of eyes, post it in Pastebin or Gist (scrubbing any private data) and share it here.

~Sarah-Beth

[Ebinezar Prawin]

Hi Sarah-Beth,

My apologies for the late reply. Yes, I'm using "lis_outcome_service_url" only, that's typo error. Even though, I have checked the log, but I can't figure out the "Error while deserializing request xml". Below I have mentioned the request xml and response xml. Also once again I'm mentioning, I'm doing all these things in trial.brightspace.com.

Request XML

<?xml version = "1.0" encoding = "UTF-8"?>  

<imsx_POXEnvelopeRequest xmlns = "http://www.imsglobal.org/lis/oms1p0/pox">      

<imsx_POXHeader>         

<imsx_POXRequestHeaderInfo>            

<imsx_version>V1.0</imsx_version>  

<imsx_messageIdentifier>544e00e7429ec</imsx_messageIdentifier>         

</imsx_POXRequestHeaderInfo>      

</imsx_POXHeader>      

<imsx_POXBody>         

<replaceResultRequest>            

<resultRecord>

<sourcedGUID>

<sourcedId>97d71712-3f06-4fd7-b5b7-a50967d53fa9</sourcedId>

</sourcedGUID>

<result>

<resultScore>

<language>en-us</language>

<textString>1</textString>

</resultScore>

</result>

</resultRecord>       

</replaceResultRequest>      

</imsx_POXBody>   

</imsx_POXEnvelopeRequest>

Response XML

<?xml version="1.0"?>

<imsx_POXEnvelopeResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.imsglobal.org/services/ltiv1p1/xsd/imsoms_v1p0">

  <imsx_POXHeader>

    <imsx_POXResponseHeaderInfo>

      <imsx_version>V1.0</imsx_version>

      <imsx_messageIdentifier />

      <imsx_statusInfo>

        <imsx_codeMajor>unsupported</imsx_codeMajor>

        <imsx_severity>error</imsx_severity>

        <imsx_description />

        <imsx_messageRefIdentifier>9e3a4d7f-3b03-44c0-8a6e-031283d76aff</imsx_messageRefIdentifier>

        <imsx_operationRefIdentifier />

        <imsx_codeMinor>

          <imsx_codeMinorField>

            <imsx_codeMinorFieldName>TargetEndSystem</imsx_codeMinorFieldName>

            <imsx_codeMinorFieldValue>unsupportedLISoperation</imsx_codeMinorFieldValue>

          </imsx_codeMinorField>

        </imsx_codeMinor>

      </imsx_statusInfo>

    </imsx_POXResponseHeaderInfo>

  </imsx_POXHeader>

  <imsx_POXBody />

</imsx_POXEnvelopeResponse>

[Desire2Learn Staff: Sarah-Beth]

Hi Ebinezar

It would also be helpful to see a trace using a utility like Fiddler so that we can see exactly what is being sent and received. you can send this trace to the Valence Inbox rather than posting it here.

~Sarah-Beth

[Desire2Learn Staff: Sarah-Beth]

To close the loop on this issue, we did discover a resolution.  The developers here noticed that the XML namespace declaration appeared to be different from what’s specified in the IMS LTI specification. Ebinezar confirmed that updating the namespace declaration resolved their issue.

In the standard, here’s the example replaceResult request block:

<?xml version = "1.0" encoding = "UTF-8"?>

<imsx_POXEnvelopeRequest xmlns = "http://www.imsglobal.org/services/ltiv1p1/xsd/imsoms_v1p0">

  <imsx_POXHeader>

    <imsx_POXRequestHeaderInfo>

      <imsx_version>V1.0</imsx_version>

      <imsx_messageIdentifier>999999123</imsx_messageIdentifier>

    </imsx_POXRequestHeaderInfo>

  </imsx_POXHeader>

  <imsx_POXBody>

    <replaceResultRequest>

      <resultRecord>

        <sourcedGUID>

          <sourcedId>3124567</sourcedId>

        </sourcedGUID>

        <result>

          <resultScore>

            <language>en</language>

            <textString>0.92</textString>