After an outage on September 1, the Instructure Community is now fully available, including guides, release notes, forums, and groups. If some styling still looks unusual, clear your cache and cookies.
Found this content helpful? Log in or sign up to leave a like!
Hi everyone
I am creating an LTI 1.3 Tool that calls Canvas's names and roles service, specifically the following endpoint
/api/lti/course/:course_id/names_and_roles
One would assume that :course_id in this endpoint could mean both Canvas's id for the course as well as the LTI 1.3 context_id that is returned in the request.
However when using the LTI1.3 course id, the request simply returns 404 resource not found.
See here the difference:
Calling with ID = 1. (Canvas course ID)
Calling with the LTI1.3 context id
Is this the intended outcome? Is this a bug?
I don't understand why this wouldn't support the context_id since using Canvas's own id just means more overhead for the developers.
Great thanks if any fellow developer can provide any help.
Regards
Atli Gislason
I just realized that the id_token from the openid login does give the following endpoint path for the names and roles service
This solves my issue, apologies if I sounded rude in my question above.
Best regards,
Atli Gislason
To interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign inTo interact with Panda Bot, our automated chatbot, you need to sign up or log in:
Sign in