The client_id will be the numeric value of the developer key you’ve pre-created for use with your tool. For example, we’ve created a developer key for our REST API web utility in the “Developer Keys” ...

Greetings,We're trying to develop a v1.3 LTI tool that utilizes the Names and Roles Provisioning Service. When we query the api URL, the result we get for user_id does not seem to be as expected.....

You could probably update the SIS ID for these existing user accounts using REST... I know it's a user attribute that you can set/update using the REST API. If you're not already using REST fo...

Edit:Unfortunately, we're STILL at an impasse as the recommended custom variable $vnd.instructure.User.uuid still does not match the original LTI v1.1 user_id launch field. So, at this point, the ...

That would be a brilliant solution if it works! I haven't tried the merge user functionality yet, but it certainly looks like it would work! Thanks for that excellent suggestion.

Anuraq,It should be as simple as querying /api/lit/courses//names_and_roles and looking at the “members” values. Each object should have a user_id value.William DiehlAnalyst/Programmer(951) 222-8396

Can you clarify how LTI 1.1 user_id launch values are translated in LTI 1.3? We've been struggling with an incompatibility with LTI 1.3's Names and Roles roster membership user ids not being c...

Edit:Unfortunately, we're STILL at an impasse as the recommended custom variable $vnd.instructure.User.uuid still does not match the original LTI v1.1 user_id launch field. So, at this point, the ...

Thanks Atli! That's a great suggestion, but unfortunately in our case we're trying to use the Names and Roles Provisioning Service to pull the user_ids of each student on the course roster, no...

Just a follow up on the Canvas support response. After escalating the ticket to tier 2, the team was very helpful in recognizing the issue (see the comments by Jesse below) and posing a possible futur...