I am developing an LTI 1.3, however for all my resource instances I get the same resourceLink, which has the context ID as an identifier. Why does this happen? Defining the scope for my lti:I am curre...

I'm a little late, I've been away from LTI development.I appreciate your answer, but in my case it was correctly forming the JWT and canvas if it gave me the token (For the client_credentials flow) bu...

This problem was solved by canvas many months ago, it was not documented and it caused us problems at the time. Since then we have had no problems with duplicate keys. Canvas recently announced the mo...

We escalated the problem, they agreed to refer it to the technical team and we never received an answer. Some time ago they fixed it arbitrarily without warning, that corrupted our tools because all t...

@DavidBrooks  After this publication, I got in touch with the person in charge of canvas in my institution, who can talk and manage things with instructure, we sent emails and the company was told, th...

This problem was solved by canvas many months ago, it was not documented and it caused us problems at the time. Since then we have had no problems with duplicate keys. Canvas recently announced the mo...

We escalated the problem, they agreed to refer it to the technical team and we never received an answer. Some time ago they fixed it arbitrarily without warning, that corrupted our tools because all t...

I'm a little late, I've been away from LTI development.I appreciate your answer, but in my case it was correctly forming the JWT and canvas if it gave me the token (For the client_credentials flow) bu...

@DavidBrooks  After this publication, I got in touch with the person in charge of canvas in my institution, who can talk and manage things with instructure, we sent emails and the company was told, th...

I am developing an LTI 1.3, however for all my resource instances I get the same resourceLink, which has the context ID as an identifier. Why does this happen? Defining the scope for my lti:I am curre...