| | 1 | Submitted by [https://www.clarin.eu/user/1937 Martin Matthiesen] on 05 November 2014 |
| | 2 | |
| | 3 | These are the minutes of the Clarin [https://www.clarin.eu/glossary#AAI AAI] TF Soesterberg meeting 24.10.2014 17:15-18:30 CET. |
| | 4 | |
| | 5 | Participants: Sander Maijers (from 17:30) Jozef Misutka, Oliver Schonefeld, Martin Matthiesen (chair & minutes), Paul Meurer (U Bergen), Mitchell Seaton (U Copenhagen) |
| | 6 | |
| | 7 | Excused: Thomas Kisler, Kai Zimmer, Dieter Van Uytvanck, Lene Offersgaard |
| | 8 | |
| | 9 | |
| | 10 | == Agenda == |
| | 11 | |
| | 12 | 1. Formalia: Agreeing on agenda, secretary |
| | 13 | 1. Action points from last meeting |
| | 14 | 1. Service Level Agreements for AAI services |
| | 15 | 1. Quality Assurance issues |
| | 16 | 1. Security level checks |
| | 17 | 1. Regular monitoring |
| | 18 | 1. eduGAIN as [https://www.clarin.eu/glossary#SP SP] requirement |
| | 19 | 1. Action points for next meeting |
| | 20 | 1. Next meeting |
| | 21 | |
| | 22 | == Action pointsfrom last meeting == |
| | 23 | |
| | 24 | * Martin, Oliver, Sander: Metadata aggretation SPF |
| | 25 | * Implemented, but has some issues: The feed would need to be aggregated for each national federation (excluding entries that SPs get through their national metadata stream anyway). |
| | 26 | * Dieter, Sander, Jozef: Promote the [https://www.clarin.eu/glossary#IdP IdP]-Validator |
| | 27 | * I also promoted in in eduGAIN and it will be used there as well. |
| | 28 | * Thomas: Hook up BAS with the SPF |
| | 29 | * Skipped. |
| | 30 | * Martin: https://wiki.edugain.org/CLARIN; Contact Feide to accept the CoC. |
| | 31 | * There has been mail contact, got cut of by holidays. A request was sent to all Home Institutions. (Outcome after the meeting: 2 HO's are connected.) |
| | 32 | * Dieter: Promote the SPF in Zürich.; Contat Feide to opt-in to the SPF. |
| | 33 | * Skipped. |
| | 34 | |
| | 35 | == Service Level Agreements for AAI services == |
| | 36 | The [https://www.clarin.eu/glossary#SCCTC SCCTC] discussed Service Level Agreements for central Clarin services. The taskforce identfied the following services as within our scope: |
| | 37 | |
| | 38 | |
| | 39 | * Disco Juice |
| | 40 | * Clarin homeless IdP |
| | 41 | * SPF-Metadata availability |
| | 42 | |
| | 43 | We will help define appropriate SLA parameters for these services. |
| | 44 | |
| | 45 | |
| | 46 | == Quality Assurance issues == |
| | 47 | We discussed constant monitoring from 2 viewpoints: Security and General Availability. |
| | 48 | |
| | 49 | |
| | 50 | === Security === |
| | 51 | Oliver suggested we help to make sure that Clarin SPs are up-to-date with respect to current security threats like Heartbeat, Shellshock, SSLv3 and the like. The general sentiment was that such tracking such issues centrally fall out of the scope of this task force, a separate security taskforce would be needed to put proper protocols in place. What we can and should do is document the incident response protocols and procedures on a national level. Some centres have such procedures in place and Clarin monitoring would be an unneccessary extra layer. We also decided to raise awarness, it was left open, in what form. |
| | 52 | |
| | 53 | |
| | 54 | === General Availabilty === |
| | 55 | It has become aparent that AAI services need close monitoring, SAML2 has just too many moving parts. We all agreed that monitoring is a good idea, we did not go into detail, what the right level would be. The tools and procedures developed at Lindat deserve a closer look. |
| | 56 | |
| | 57 | |
| | 58 | == eduGAIN as SP requirement == |
| | 59 | This topic came up during the meeting. Keeping the metadata up-to-date is a real challenge for the SPF, requiring SPs to join eduGAIN would make this task much easier. We did discuss the issue for quite a bit, since bringing this to the SCCTC relatively shortly after the !CoCo requirement approval might be polically difficult. There are, however, quite a few good arguments for such a requirement. We decided to formulate a SCCTC proposal to be discussed and decided upon in the the next AAI TF meeting. |
| | 60 | |
| | 61 | |
| | 62 | == Action points for next meeting == |
| | 63 | These were not discussed in the meeting but derived from the topics discussed: |
| | 64 | |
| | 65 | |
| | 66 | * Old APs |
| | 67 | * Thomas: Hook up BAS with the SPF |
| | 68 | * Dieter: Promote the SPF in Zürich.; Contat Feide to opt-in to the SPF. |
| | 69 | * Define appropriate SLA for AAI services (owners to be decided in next meeting) |
| | 70 | * SP Security: Raise awareness (owners to be decided next meeting) |
| | 71 | * General Availability monitoring (proposal for next meeting needed) |
| | 72 | * eduGAIN as SP requirement, formulate proposal for next meeting. Owners so far: Martin |
| | 73 | |
| | 74 | == Next meeting == |
| | 75 | We agreed to meet rather promptly hopefully in November. |
