LTI 1.3 Get "names_and_roles" does not return all records

[matthew_buckett · Accepted solution]

We have a couple of integrations that use the Names and Roles Provisioning Service in canvas and when there are more than 50 people in the course we get a paginated set of results back. I think that the calls to endpoint only return users who have accepted their invitation to the course, so if you are testing by manually enrolling users into the course, they have to accept their invitation to the course to show up in the results. If they are showing as "pending" in the People tool they don't get included in the JSON.

[LiamMoran]

When synchronizing rosters, Canvas only provides 50 course participants. I haven't found a workaround: I thought that setting a high limit parameter to the api endpoint for this would work, but it takes the mimimum of its' default of 50 and whatever value of limit you provide. It's not sending a LINK header for paginated results. What are we missing here?

[matthew_buckett · Accepted solution]

We have a couple of integrations that use the Names and Roles Provisioning Service in canvas and when there are more than 50 people in the course we get a paginated set of results back. I think that the calls to endpoint only return users who have accepted their invitation to the course, so if you are testing by manually enrolling users into the course, they have to accept their invitation to the course to show up in the results. If they are showing as "pending" in the People tool they don't get included in the JSON.

[LiamMoran]

One live course that I'm looking at now has 111 people in the course and only 2 enrollments are pending per the People tool. The Limit parameter does work: I passed limit=49 and it sent back 49 students.

Looking at it again, I do see a "link" header but it's empty in the debugging output that I see.

It's very reassuring that you've seen enrollments over 50 work with this endpoint, so I'll presume that the http header isn't being parsed correctly and fixing that will get me back in business.

[LiamMoran · Accepted solution]

OK: I can confirm that the link header is being parsed incorrectly by the tool I'm working on.

Thanks for helping get me on the right track, Matthew.

[matthew_buckett]

Happy to help, and good to hear you're making forward progress again.