Currently to construct the internal globally unique tool identifier for an incoming LTI2 tool registration, we make use of the product_family code and the vendor code as well as the resource_type code. This makes no sense as the product_family and vendor codes as indicators of what software is being rung are likely to the the same across lots of intances of a tool hosting container like Tsugi.
So the new tool registration will be based on the
Which Per the LMS LTI 2.0 spec is "A globally unique identifier for the service provider. As a best practice, this value should match an Internet domain name assigned by ICANN, but any globally unique identifier is acceptable."
The guid will be concatenated with the resource_type code.
This will apply to new registrations. Since re-registration is an LTI 2.1 concept it is not yet supported and the primary place this matters is during re-registration.