Changes between Version 4 and Version 5 of Taskforces/AAI/Meetings/2021-06-10
- Timestamp:
- 06/14/21 08:37:26 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Taskforces/AAI/Meetings/2021-06-10
v4 v5 4 4 5 5 = Topics = 6 7 6 == AAI Proxy == 8 [[BR]]Willem presented the idea to introduce an AAI proxy similar to Elixir. 7 [[BR]]Willem presented the idea to introduce an AAI proxy similar to Elixir. 9 8 10 9 Benefits: 11 10 12 * Once accepted by a Federation CLARIN can give SPs more assurances that connect will work and even provide missing IdP attributes. 11 * Once accepted by a Federation CLARIN can give SPs more assurances that connect will work and even provide missing IdP attributes. 13 12 * OIDC/OAuth2 -bridging is possible 14 13 * Much easier administration than present SPF, especially on CLARIN ERIC side … … 18 17 * Self-reported attributes (e.g. mail) must be visible as such to SPs 19 18 * SPs using targetedID, or any other approach using (IDP,SP) specific information, cannot identify returning users (some workaround for this will be needed) 19 * Jozef: At the moment, I would highlight this as a show stopper to Clarin IdP revolution (mandatory moving to hub&spoke for all SPs) but not a showstopper to potential Clarin IdP evolution (mandatory for new SPs).[[BR]]And it is not only about targetedID but can be also for idp+eppn and probably other combinations. 20 20 * Single point of failure 21 21 * Proxies proxying to proxies might confuse users. … … 24 24 25 25 == Lindat's Attribute Aggregator == 26 27 26 The "AAGREG" was introduced a few years ago, uptake is low. It is seen as a useful tool and we agreed to promote uptake in the next SCCTC. 28 27 29 28 == SP-specific discovery services == 30 31 29 There is a need for SP-specific discovery service feeds, CLARIN is aware of the issue and more information is to follow. 32 30 33 31 == API Security == 34 35 32 A brief overview of API tokens and their usage was presented.
