...
| Title | update SAML tracer - get this done in GN4-2 |
|---|---|
| Description | The SAML Tracer (https://addons.mozilla.org/nl/firefox/addon/saml-tracer/) is a highly rated firefox plugin which was developed in our community (UNINETT, with contributions from others). As the browser is the central entity in any SAML transaction, it is extremely convenient tool for testing en debugging SAML transactions. There are not many alternatives to this tool Unfortunately, Firefox has changed its plugin framework, rendering the existig plugin useless and a major rework is needed. |
| Proposer | Niels van Dijk, SURFnet |
| Resource requirements | Money, a (junior) developer |
| +1's | Stefan Winter Scott Koranda, LIGO Nick Roy, InCommon Thomas Lenggenhager, SWITCH:Feasibility to provide also a version for Safari compatible version? Thanks José Manuel, I now found the SAML Chrome Panel! Pieter van der Meulen (SURFnet) Michael Domingues (University of Iowa) José Manuel, RedIRIS/SIR. Regarding Thomas question, there's a SAML Chome Panel extension for Chrome Wolfgang Pempe, DFN MIchael Brogan (University of Washington) Nate Klingenstein (The California State University) Marcus Mizushima (The California State University) Andrew Morgan (Oregon State University) David Bantz (U Alaska) Brent Putman (Georgetown University, Shibboleth Developer Team) Liam Hoekenga (University of Michigan) Terry Smith (AAF) Dalia Abraham (AAF) Daniel Lutz (SWITCH) Etienne Dysli Metref (SWITCH) Martin Haase (DAASI) Rod Widdowson (Steading System Software, Shibboleth Developer Team) Allan West (University of Florida) Dominique Petitpierre (University of Geneva) Cédric BRINER (University of Geneva) Eric Yurick (Gettysburg College) Vlad Mencl (Tuakiri/REANNZ) |
eduroam
...
eduroam SP-as-a-service
...
With eduroam Managed IdP, there is a service which takes all RADIUS hassle off of Identity Providers. There is no equivalent for eduroam SPs. I.e. a future eduroam SP either needs to set up a local RADIUS server and connect it to the NRO, or (if the NRO supports it) connect the Wireless Controller directly to an NRO server - losing all advanced features such as VLAN assignment. For small hotspots, there is a possible additional complication if the hotspot has a dynamic IP address, which makes the interconnection via RADIUS' shared secrets infeasible. Right now, such potential hotspots are not serviceable by eduroam infrastructure.
The goal of this activity is to create a self-service web portal where any prospect SP can register his hotspot (requiring sign-off by the NRO; comparable to eduroam Managed IdP) - regardless whether he has a static IP address, a dynamic one, or doesn't even know what an IP address is in the first place. The new hotspot's RADIUS connectivity is tested in real-time (e.g. using a credential from eduroam Managed IdP, a good complement to this service) and the new SP is instantly connected to the eduroam infrastructure. Where the NRO admin confirms that a particular hotspot maps to a specific realm or Managed IdP instance, the SP can even get VLAN ID assignments for his own users (that part of the use case is possibly a bit weak as an SP who does not know about setting up a RADIUS server likely also doesn't know about VLANs to begin with).
For the technicalities of the uplink itself, there should be support for multiple attachment anchors (=RADIUS servers behind the web interface) because geographical proximity to the hotspot is important for performance reasons.
The remaining complexity for the SP which this service will not take away is: phyiscal installation of APs, controllers, and the configuration of those so that they are providing proper local eduroam.
To ensure service quality on such "no clue" SPs, it could be made mandatory to install a probe at the site so eduroam Operations can monitor the hotspot quality.
...
VM for web interface, VMs for RADIUS attachment anchors, a clever idea how to handle registering hotspots with dynamic or unknown IPs
...
eduroam DEEP Learning
...
I'll give this one a "sounds cool, need more info" Nick Roy, InCommon
Can be integrated via existing diagnostics context: Existing work evaluation#eduroamdiagnostics so gets a +1 from prior endorsements too. (note from AH)
Should x-ref with the network perf folk. Talk to Kurt Baumann(Note from AH).
Georgi Tsochev, BREN
Rhys Smith, UKf: Wot Nick said.
I prefer any machine learning method rather than "just" Deep Learning, although the name is more appealing. (Hideaki Goto, NII)
Above and Below eduGAIN (inc. eScience requirements driven activities)
| Title | Placeholder to include (and potentially continue) some of AARC work |
|---|---|
| Description | I would like to have a placeholder to include work that my be triggered by the revisited list of FIM4R requirements, as well as by AARC. Furthermore, I'd also like to include in this box liaisons with EOSC hub concerning their T&I architecture developments and adoption/support of FIM technologies. This item cannot and should not be more specific than this at this point in time. |
| Proposer | Licia Florio |
| Resource requirements | Coordination work, resources |
| +1's | <for others to voice their support - add your name here> |
| Title | eduTEAMS enhancements |
|---|---|
| Description | eduTEAMS work is progressing; there are different options for deploying eduTEAMS. This work item looks at the requirements for eduTEAMS when used by eScience collaborations. There will be lessons learned after the pilot with the life science community. I propose we have a placeholder so work on this does not go off radar during the planning. |
| Proposer | Licia Florio |
| Resource requirements | Effort mostly |
| +1's | <for others to voice their support - add your name here> |
| Title | Discovery for Attribute Authorities (AAs) |
|---|---|
| Description | Users can select their IdP via discovery, therefore the SP can potentially receive users from thousands of IdPs. There is no such facility for AA-s however, meaning that SP-s need to hard-configure which AAs they query. Also, query all the configured AAs for all users all the time. In GN4-1-JRA3-T1 it has been established that this is a serious bottleneck, as maximum 2-3 AAs can be queried without breaking the entire login session. A better approach is needed. The SPs need to query AAs selectively, based on either user input or some alternative means, like some VO lookup service. Otherwise all SPs will just stick with the biggest AAs like eduTEAMS basic membership service or hexaa.eduid.hu and not query alternative entities, making single-tenant AAs very unattractive. |
| Proposer | Mihály Héder |
| Resource requirements | This is a hard one. Currently there is no support for any elements of this whatsoever
|
| +1's | Constantin Sclifos, RENAM |
| -1's | Wolfgang Pempe, DFN: Such a dynamic approach would raise issues concerning trust and privacy. An attribute authority must be in control of the list of SPs that are entitled to perform attribute queries and (possibly) recieve PII. |
| Title | eduTEAMS and guest IdPs |
|---|---|
| Description | eduTEAMS and guest IdPs - use-cases: need to support social IDs and guest IdP, but it need additional LoA. Step up authN as a service is in the plan |
| Proposer | from data gathering exercise |
| Resource requirements | <money? effort? coordination? infrastructure?> |
| +1's | isn't this the work being done in IoLR +REFEDS? |
eduroam
| Title | eduroam SP-as-a-service |
|---|---|
| Description | With eduroam Managed IdP, there is a service which takes all RADIUS hassle off of Identity Providers. There is no equivalent for eduroam SPs. I.e. a future eduroam SP either needs to set up a local RADIUS server and connect it to the NRO, or (if the NRO supports it) connect the Wireless Controller directly to an NRO server - losing all advanced features such as VLAN assignment. For small hotspots, there is a possible additional complication if the hotspot has a dynamic IP address, which makes the interconnection via RADIUS' shared secrets infeasible. Right now, such potential hotspots are not serviceable by eduroam infrastructure. The goal of this activity is to create a self-service web portal where any prospect SP can register his hotspot (requiring sign-off by the NRO; comparable to eduroam Managed IdP) - regardless whether he has a static IP address, a dynamic one, or doesn't even know what an IP address is in the first place. The new hotspot's RADIUS connectivity is tested in real-time (e.g. using a credential from eduroam Managed IdP, a good complement to this service) and the new SP is instantly connected to the eduroam infrastructure. Where the NRO admin confirms that a particular hotspot maps to a specific realm or Managed IdP instance, the SP can even get VLAN ID assignments for his own users (that part of the use case is possibly a bit weak as an SP who does not know about setting up a RADIUS server likely also doesn't know about VLANs to begin with). For the technicalities of the uplink itself, there should be support for multiple attachment anchors (=RADIUS servers behind the web interface) because geographical proximity to the hotspot is important for performance reasons. The remaining complexity for the SP which this service will not take away is: phyiscal installation of APs, controllers, and the configuration of those so that they are providing proper local eduroam. To ensure service quality on such "no clue" SPs, it could be made mandatory to install a probe at the site so eduroam Operations can monitor the hotspot quality. |
| Proposer | Stefan Winter |
| Resource requirements | VM for web interface, VMs for RADIUS attachment anchors, a clever idea how to handle registering hotspots with dynamic or unknown IPs |
| Comments | Rhys Smith, UKf: just to say that Jisc Liberate, our managed SAML IdP/eduroam IdP/eduroam SP/ABFAB IdP/ABFAB SP/web proxy service, will have the eduroam SP bit towards the start of 2018. Stefan's description is a slightly different use case, however, so I think it doesn't really overlap here. |
| +1's | Rhys Smith, UKf: sounds like a good way to get new visited eduroam sites on board. |
| Title | eduroam DEEP Learning |
|---|---|
| Description | Based on Brooks idea, we train a DEEP network to detect eduroam breakage based on log-data. Possible joint work with Juniper Research. Leif will provide more information |
| Proposer | Leif |
| Resource requirements | To be better scoped, but certainly resources. |
| +1's | I'll give this one a "sounds cool, need more info" Nick Roy, InCommon Can be integrated via existing diagnostics context: Existing work evaluation#eduroamdiagnostics so gets a +1 from prior endorsements too. (note from AH) Should x-ref with the network perf folk. Talk to Kurt Baumann(Note from AH). Georgi Tsochev, BREN Rhys Smith, UKf: Wot Nick said. I prefer any machine learning method rather than "just" Deep Learning, although the name is more appealing. (Hideaki Goto, NII) |
| Title | Scale eduroam infrastructure to the size of WIFI4EU |
|---|---|
| Description | There were a multitude of reasons why the GÉANT community couldn't run the infrastructure for WIFI4EU. Sufficient issues were exposed by managing this as a single centrailsed infrastructure (partially addressed by "get eduroam", "eduroam DEEP Learning", "eduroam SP-as-a-Service"). By identifying all the scaling blocks to existing eduroam services we'd be able to offer advice, guidance and technology push into govroam, WIFI4EU and eduroam services to support the existing infrastructure and development in new territories. |
| Proposer | Brook |
| Resource requirements | People |
| +1's | Georgi Tsochev, BREN Reimer Karlsen-Masur, DFN-PKI Great chance to accelerate the deployment of secure public Wi-Fi systems in the world and to inter-connect them. Related to my proposal of inter-roaming, but a separate work item dedicated to WiFi4EU is still preferred. (Hideaki Goto, NII) |
| Title | Develop inter-roaming architecture and "eduroam on NGH" |
|---|---|
| Description | Develop an inter-roaming architecture that connects various Roaming Consortia (RC) including eduroam, govroam, City Wi-Fi (secured), WiFi4EU, etc. to enable roaming, with or without Passpoint. Make the deployment of off-campus eduroam/govroam services much easier. For example, eduroam accounts can be enabled on City Wi-Fi world-wide. Contribute to the improvement of Hotspot 2.0 to make "eduroam on NGH" possible. (The current HS2.0 specifications and some implementations are known to have some issues hampering large RC creation.) Contribute to the revisions of the WRIX specifications to make them as much compatible as possible with eduroam's. WRIX-i (interconnect) and WRIX-L (location) are the targets. |
| Proposer | Hideaki Goto, NII (out of EU :) |
| Resource requirements | people, (more official and stronger) collaborative work with WBA, human network with WiFi4EU, WBA member fee if required |
| +1's | <for others to voice their support - add your name here> |
Future Certificate Services
| Title | certbot for all certificate management |
|---|---|
| Description | Let's Encrypt and the certbot have made certificate management for 1 particular CA very easy and effective. With the addition of ACME v2 this will allow additional CAs to participate and allow the dev/test/production environments to automatically deal with certificates. Work should also investigate eduPKI and Let'sRADSEC use of this mechanism for certificate maintenance. TechEx 2016 ACAMP notes: https://docs.google.com/document/d/1o20NmuLjmNySp10QqfueO3of6jmoeTRfmgG4e_olZ_s/edit |
| Proposer | Brook (and a cast of thousands) |
| Resource requirements | People, Money, work to get standardisation of "realm validated certificates via RADIUS infrastructure" and maybe other paths. |
| +1's | Georgi Tsochev, BREN Rhys Smith, UKf: Certbot is going to take over the world, so we should start doing stuff with it. Reimer Karlsen-Masur, DFN-PKI |
| Title | cryptech.is |
|---|---|
| Description | |
| Proposer | |
| Resource requirements | |
| +1's |
| Title | CA CAB/Browser forum participation |
|---|---|
| Description | |
| Proposer | |
| Resource requirements | |
| +1's |
Attribute Authorities
| Title | Attribute Authority scoping information in Metadata |
|---|---|
| Description | It seems that AARC-JRA1.4A will propose "scoping of group membership information". However, there is no element in the SAML metadata that contains the scope of an AA, therefore, there is nothing to verify the scoped membership information against. The only way today is to learn about the scopes used by an AA entity via word-of-mouth and then apply those scopes in attribute value level filtering and access control rules, maintained manually in the SP config. Obviously this does not scale. |
| Proposer | Mihály Héder |
| Resource requirements |
|
| +1's |
| Title | Attribute Authority Metadata policy development for eduGAIN |
|---|---|
| Description | While for IdPs and SPs eduGAIN metadata requirements are well described, no such requirements exist for AAs. We have however already 5 of these entities in eduGAIN. It would also be a good idea to consider/define what it would mean for an AA to claim CoCo, R&S and Sirtifi support |
| Proposer | Niels van Dijk |
| Resource requirements |
|
| +1's | Constantin Sclifos, RENAM Nick Roy, InCommon SURFnet Rhys Smith, UKf: I think AAs will become more important as we move forward, and there is a gap here in policy that needs thinking about. |
...
Scale eduroam infrastructure to the size of WIFI4EU
...
There were a multitude of reasons why the GÉANT community couldn't run the infrastructure for WIFI4EU.
Sufficient issues were exposed by managing this as a single centrailsed infrastructure (partially addressed by "get eduroam", "eduroam DEEP Learning", "eduroam SP-as-a-Service"). By identifying all the scaling blocks to existing eduroam services we'd be able to offer advice, guidance and technology push into govroam, WIFI4EU and eduroam services to support the existing infrastructure and development in new territories.
...
Georgi Tsochev, BREN
Reimer Karlsen-Masur, DFN-PKI
Great chance to accelerate the deployment of secure public Wi-Fi systems in the world and to inter-connect them. Related to my proposal of inter-roaming, but a separate work item dedicated to WiFi4EU is still preferred. (Hideaki Goto, NII)
...
Develop inter-roaming architecture and "eduroam on NGH"
...
Develop an inter-roaming architecture that connects various Roaming Consortia (RC) including eduroam, govroam, City Wi-Fi (secured), WiFi4EU, etc. to enable roaming, with or without Passpoint.
Make the deployment of off-campus eduroam/govroam services much easier. For example, eduroam accounts can be enabled on City Wi-Fi world-wide.
Contribute to the improvement of Hotspot 2.0 to make "eduroam on NGH" possible. (The current HS2.0 specifications and some implementations are known to have some issues hampering large RC creation.)
Contribute to the revisions of the WRIX specifications to make them as much compatible as possible with eduroam's. WRIX-i (interconnect) and WRIX-L (location) are the targets.
...
Future Certificate Services
...
certbot for all certificate management
...
Let's Encrypt and the certbot have made certificate management for 1 particular CA very easy and effective. With the addition of ACME v2 this will allow additional CAs to participate and allow the dev/test/production environments to automatically deal with certificates.
Work should also investigate eduPKI and Let'sRADSEC use of this mechanism for certificate maintenance.
TechEx 2016 ACAMP notes: https://docs.google.com/document/d/1o20NmuLjmNySp10QqfueO3of6jmoeTRfmgG4e_olZ_s/edit
...
Georgi Tsochev, BREN
Rhys Smith, UKf: Certbot is going to take over the world, so we should start doing stuff with it.
Reimer Karlsen-Masur, DFN-PKI
...
cryptech.is
...
CA CAB/Browser forum participation
...
Attribute Authorities
...
Discovery for Attribute Authorities (AAs)
...
Users can select their IdP via discovery, therefore the SP can potentially receive users from thousands of IdPs.
There is no such facility for AA-s however, meaning that SP-s need to hard-configure which AAs they query. Also, query all the configured AAs for all users all the time.
In GN4-1-JRA3-T1 it has been established that this is a serious bottleneck, as maximum 2-3 AAs can be queried without breaking the entire login session.
A better approach is needed. The SPs need to query AAs selectively, based on either user input or some alternative means, like some VO lookup service. Otherwise all SPs will just stick with the biggest AAs like eduTEAMS basic membership service or hexaa.eduid.hu and not query alternative entities, making single-tenant AAs very unattractive.
...
This is a hard one. Currently there is no support for any elements of this whatsoever
- Standardization
- SAML Stack development
- blood and sweat
...
Attribute Authority scoping information in Metadata
...
- Standardization
- SAML stack development
...
Attribute Authority Metadata policy development for eduGAIN
...
While for IdPs and SPs eduGAIN metadata requirements are well described, no such requirements exist for AAs. We have however already 5 of these entities in eduGAIN.
It would also be a good idea to consider/define what it would mean for an AA to claim CoCo, R&S and Sirtifi support
...
- Standardization
- Probably a no-brainer as much can likely be derived from IdP requirements (?)
...
Constantin Sclifos, RENAM
Nick Roy, InCommon
SURFnet
Rhys Smith, UKf: I think AAs will become more important as we move forward, and there is a gap here in policy that needs thinking about.
Wolfgang Pempe, DFN
eScience requirements driven activities
...
Placehoder to include (and potentially continue) some of AARC work
...
I would like to have a placeholder to include work that my be triggered by the revisited list of FIM4R requirements, as well as by AARC. Furthermore, I'd also like to include in this box liaisons with EOSC hub concerning their T&I architecture developments and adoption/support of FIM technologies. This item cannot and should not be more specific than this at this point in time.
...
eduTEAMS
| Title | eduTEAMS enhancements |
|---|---|
| Description | eduTEAMS work is progressing; there are different options for deploying eduTEAMS. This work item looks at the requirements for eduTEAMS when used by eScience collaborations. There will be lessons learned after the pilot with the life science community. I propose we have a placeholder so work on this does not go off radar during the planning. |
| Proposer | Licia Florio |
| Resource requirements | Effort mostly |
| +1's | <for others to voice their support - add your name here> |
| Title | eduTEAMS and guest IdPs |
| Description | eduTEAMS and guest IdPs - use-cases: need to support social IDs and guest IdP, but it need additional LoA. Step up authN as a service is in the plan |
| Proposer | from data gathering exercise |
| Resource requirements | <money? effort? coordination? infrastructure?> |
| +1's | isn't this the work being done in IoLR +REFEDS? Wolfgang Pempe, DFN |