...
In model 2), a newer component--Attribute Providers or Attribute Authorities might help solve some of the challenges of TPs getting access to needed user information.
----------
Here are some further reflections:
There seemed to be general agreement with the assertion that LTI fits the definition of SSO where the TC plays the role of IdP.
Scott C noted that LTI can pass both user context and application context. There was some discussion to the effect that an application requiring both is unnecessarily constrained and constraining.
Scott C mentioned deep linking as a model for flexible support of various workflows.
All participants felt scenario 1a (from https://spaces.at.internet2.edu/x/qgEVAg
) applies. Several are interested in scenario 1c. Yours truly is also interested in 1b (our portal does not suck all that much)
The group used the two examples to illustrate the range of TP types (relating to Keith's points 1 and 2 below). The first is the widget that launches in the browser. The second is CourseLoad, a cloud-based etext reader that allows annotations and provides faculty with usage data for analytics. Some less comfortable with LTI for the second case.
Many acknowledged that LTI is essential to support LMSs and allows for independent tools and a multi-LMS environment.