Keyset URL cannot be reached

Scott.H.223
Scott.H.223 Posts: 8 Analytics Builder Transition
edited March 18 in Development

I'm trying to setup an LTI advantage link with Mahara on our test environment but after completing all the details as instructed on the Mahara help pages here:

https://manual.mahara.org/en/21.10/external/lti_brightspace.html#ltiadvantage-brightspace

 

Brightspace returns a Keyset URL cannot be reached error.

 

Any ideas what I might be doing wrong?

Tagged:
· Share on Twitter

Answers

  • Rusha.S.831
    Rusha.S.831 Posts: 130
    edited November 2022

    Hello @Scott Hedger​ ,

     

    Thank you for contacting us via Brightspace Community!

     

    May I suggest you open a support ticket with us to further look into this issue that you are experiencing?

     

    Kind Regards,

    Rusha

     

     

     

     

    · Share on Twitter
  • Scott.H.223
    Scott.H.223 Posts: 8 Analytics Builder Transition
    edited November 2022

    In case anyone runs into a similar problem in the future. Our Mahara test site was hosted on a LAN which our Brightspace test server couldn't contact. We had to move the Mahara test site to a publicly accessible server before we could complete the Mahara LTI integration.

    · Share on Twitter
  • Andy.G.943
    Andy.G.943 Posts: 2 🔍
    For me it was because my server only supports TLS 1.3 and Brightspace doesn't support TLS 1.3. I had to host my JWKS somewhere else.
    · Share on Twitter
  • Jeff.C.963
    Jeff.C.963 Posts: 1 🌱

    My server was also using TLS 1.3. Originally I had "SSLProtocol TLSv1.2 TLSv1.3" line in my apache default.conf file. Even though requests should have automatically assigned the correct TLS version based on the request, it was defaulting to version 1.3. Once I changed the apache default.conf file to remove the TLSv1.3 it worked. The final directive in the .conf file that worked was:

        SSLProtocol TLSv1.2

    · Share on Twitter

Categories