NRPS Issues

[Chris Filkins]

Good morning fellow Tsugi developers :D  I'm trying to troubleshoot an issue I'm having with NRPS with Canvas.  

In my module, I'm using this simple call:

$nrps = $CONTEXT->loadNamesAndRoles(true);

Looking at the debug data, my dev instance returns an oauth token successfully...

        "Token Url: https:\/\/canvas.instructure.com\/login\/oauth2\/token",

 but for production I'm getting a 500 error response.  Any ideas why Canvas would throw a 500 error for one and not the other?

-Chris

[Chuck Severance]

Chris,

Not an expert on NRPS - but one thing that has been a problem with SakaiPlus talking to Canvas is before and after a course is published.  A lot of stuff breaks before a course is published.  Which is kind of bad because you need to publish to test.

Hope that  helps.

/Chuck

--
You received this message because you are subscribed to the Google Groups "Tsugi Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tsugi-dev+...@apereo.org.
To view this discussion visit https://groups.google.com/a/apereo.org/d/msgid/tsugi-dev/d5034a23-59d3-42d7-9e19-6d29dd2f4a45n%40apereo.org.

[Chris Filkins]

Thanks!  

I _think_ I've found the issue - Canvas isn't happy with the JWKS url, at least not anymore (it worked fine during initial testing/review two months ago).  I pulled the first key out of the url and put just the single key into the setup in Canvas, and now it's returning a key.  

-Chris

[Charles Severance]

Interestingly, the Canvas had its own proprietary public key URL format that Tsugi knows about and can produce.  Tsugi also provides a stock JWKS url that literally every LMS on the planet works with.  I wonder if there is a Canvas version thing that is looking for different stuff in its registration process,

/Chuck 

To view this discussion visit https://groups.google.com/a/apereo.org/d/msgid/tsugi-dev/CAN4-RNiF5yVS8bxo_XTUCH_R_AJSHr0W%3D6J8Fjzd4aiWVD1F6g%40mail.gmail.com.

[Chris Filkins]

What was frustrating is that it worked fine a little while back.  And it works fine against my local instance, but not production.  Prod hasn't been updated in a bit, and I'm not sure if the keys may have changed, but I guess this is also a good impetus to look at pulling my prod instance forward with the updated Tsugi code.  

-Chris

[Chris Filkins]

Just wanted to bring this back up again, should other folks run into it as well...

I just spun up a new Tsugi environment with the newest commit (at least as of 1/7/2026).  Canvas seems to be having some issues with the JSON coming out of Tsugi - I can't use the configuration URL - it throws an error, and if I paste the JSON into Canvas it'll say it's not formatted correctly (even though I've run it against multiple other validations).  So there's definitely something quirky going on with some syntax there.

I also ran into the same NRPS issue from before - the new instance only has a single jwks key, but if I use the URL the NRPS fails, and if I copy/paste the body of the key into Canvas it'll work fine.

@Charles Severance  - any thoughts about anything with encoding, or anything else that might cause Canvas to choke on the JSON coming out of Tsugi?

Thanks so much!

-Chris