...
| WORK ITEMS | DESCRIPTION | ASSIGNED TO | START DATE | END DATE | GOALS | STATUS |
|---|---|---|---|---|---|---|
| REF24-2A | Peter Brand with support from Nicole Harris | This is an ongoing discussion group and as such has no specific goals. | ||||
| REF24-2B | SPOG: SP Operators Group | Laura Paglione | This is an ongoing discussion group and as such has no goals. | |||
| REF24-2C | eduID Operators Group | Marlies Rikken | An operator group for NREN's offering an IdP service that is not bound to a specific organisation, for example as an IdP of last resort and IdP for home organisations that don't manage their own. This is a place to discuss and exchange ideas and operational guidelines. A possible first outcome could be a position paper on how eduIDs perceive themselves (what unifies the eduID?) | |||
| REF24-2D | Metadata about Federations Working Group | Pål Axelsson | To find information about federations today requires that you go to each one of them you're interested to and manually gather the information or go to eduGAIN technical site and look for what is manually registered there. This working group discusses and (may) define a metadata extension that includes information and policy links plus contact information that is published in the federation metadata feed. This will allow others to aggregate this information, for example, in MET and the technical eduGAIN site. The solution should be federation technology agnostic, with examples for both SAML and OpenID technology federations. | |||
| REF24-2E | Browser Changes and Federation | Judith Bush, Zacharias Törnblom | Provide input to APIs under development by the browser community to implement new privacy controls managed by the browser. In FedCM ("A privacy preserving federated identity Web API" - quote from GitHub) several browser vendors are working to ensure users can still use buttons for "Sign in with <third party IdP vendor>..." even as the privacy-preserving practices around third-party cookies etc. are rolled out - privacy practices that would inevitably break the current login pattern. This baseline will enable us to continue offering our R&E community federated access as long as we take part in its development, and adapt our community's critical software stacks. | |||
| REF24-2F | Update the MRPS | Alex Stuart | The current Metadata Registration Practice Statement is out of date but is still used by eduGAIN candidates. | |||
| REF24-2G | Open Science Attributes | Benn Oshrin, Alan Buxey | Supporting Open Science Through Attributes Programs such as the US Government's Open Science initiative are likely to drive requirements for attributes beyond "researcher" and "member". Resource Providers will need additional information about a person’s qualifications in order to determine access to their services. This work item intends to
| |||
| REF24-2H | SeamlessAccess Trustinfo Metadata Working Group (now Entity Selection Profile Working Group) | Alex Stuart Albert Wu | Formalise SeamlessAccess trustinfo metadata as a REFEDS specification Trustinfo metadata has been developed by the SeamlessAccess team. A working document exists and code is in development (perhaps even deployed) in SeamlessAccess. This work item is to take the specification through the REFEDS standardization process, which should facilitate uptake by federation operators. | |||
| REF24-2I | Framework Registration Working Group | Albert Wu | To define a REFEDS profile for registering support for entity categories or frameworks in metadata Today all working groups need to define if and how an entity shall indicate in metadata that they support a specific REFEDS specification. This working group will define a REFEDS framework on how this should be done. Today REFEDS entity categories and SIRTFI have this defined in their specifications but it would be good to have a specific profile on how to do this for all REFEDS frameworks, profiles, and entity categories.
|
...