Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
3.9
-
MOODLE_39_STABLE
-
MOODLE_39_STABLE
-
MDL-67612-tcguid -
Description
As a tool, I want to be able to scope context and user ids by tool_consumer_instance_guid.
The current LTI implementation uses the site host as the tool_consumer_instance_guid, for example moodle.myuni.edu. When a site gets re-installed, for example at the end of term (as per guideline https://docs.moodle.org/38/en/Year-end_procedures#Make_a_new_Moodle), the hostname remains the same, but all the ids for courses and users are reset. It is therefore impossible for tools to know if a context or user is always representing the same entity. A tool has either to coordinate with the institution to reset on both sides, or apply heuristics based on the other user's data (name) to detect a change, causing a lot of work for administrators on both side, and introducing the risk of account swap (user entering a tool under another user's account).
The proposed change is to have the tool_consumer_instance_guid be the site id and thus change on re-install, allowing the tool to uniquely map a user per (tool_consumer_instance_guid, user_id) and a context by (tool_consumer_instance_guid, context_id).
The change should not impact existing tools, as those may already rely on the current value of tool_consumer_instance_guid.
This issue was already reported under MDL-35492.
Attachments
Issue Links
- will help resolve
-
MDL-35492 tool_consumer_instance_guid not very unique
-
- Closed
-