...
Conversation Point | Applicable to any Context | Context 1: Federation centric ‘Social’ Identity Service | Context 2: Institutional centric ‘Social’ Identity Service | Context 3: Federated SP, SP centric ‘Social’ Identity Service | Context 4: Standalone Service (non federated) |
|---|---|---|---|---|---|
What are the dimensions of ongoing support for the given context? (e.g costs borne by SP's, impact to end users...) |
| ||||
How should required attributes be dealt with? |
|
|
|
|
|
When 'user' is specified, what are the possible ways to appropriately identify them with a unique identifier? |
|
|
|
|
|
What is available as data is 'passed through' to the interior environment? |
|
|
|
|
|
What are the benefits / drawbacks of running a gateway in this context? |
|
|
|
|
|
What do I have to do as a Service Provider to leverage this particular model? |
|
|
| You may have additional registrations to perform for your service for each endpoint you want to allow in |
|