REFEDS-FALL-2013

Welcome! Please note:

• https://refeds.org/about/about_agreement.html
• refeds@groupchat.nordu.net
• #REFEDS #i2identity13

Coordinated consensus

The FOP is designed to help parties understand the technical processes a federation undertakes to create the federation trust framework. It is designed to be a companion document to the federation policy document and as such should work in a similar way. As with the federation policy, sections of the FOP may point or link to other documents or parts of the federation website to demonstrate compliance or practice rather than include these processes directly in the FOP document.

"One way of looking at the documents is that policy deals with WHO can be in a federation ant WHAT they can do, whereas the FOP deals with HOW the federation ensures these rules are kept."

Attribute Release Policy

https://refeds.org/category/research-and-scholarship

(this doesn't work as a URL yet!)

"The Service Provider is a production SAML deployment that supports SAML V2.0 Web Browser SSO, in particular SAML V2.0 HTTP-POST binding."

Discussion points:

• Are we referencing SAML compliance as well as we could?
• Do we have the definition right now? Do you understand the scope?
• Further categories: affiliation.
• Further categories: library services.

A 'bucket' of entity metadata; a single place to store your entity information.

• PEER software tested: SAMLmetaJS
• Metadata Query:
• https://datatracker.ietf.org/doc/draft-young-md-query/.
• REEP MRPS and KMPS:
• https://refeds.terena.org/index.php/REEP_Policy

PEER / REEP has challenged the way we think about the structure of identity federations, the exchange of metadata and management of our policies and has taught us much about how to be good citizens in the operation of federations.

7125 Entities registered in

35 federations

S

• eResearch work: https:/ blog.refeds.org/a/161.
• RFC development.
• SAMLbits: http://samlbits.org/. (Leif if time)
• SAML f-ticks. (Leif if time).
• Code of Conduct (on agenda).

Open discussions:

• Entity Category: R&S
• Entity Categories: Library. Affiliation
• Metadata Query Specification.
• REEP Metadata Registration Practice Statement.
• REEP Key Management Practice Statement.
• FOP Structure.
• (SAMLbits).
• (F-ticks).

REF 13-2: Defining Baseline Assurance

Is a FOP Just 4 Practice Statements?

• Metadata Registration Practice Statement.
• Key Management Practice Statement.
• Assurance Practice Statement.
• Monitoring Practice Statement.

Software Dev:

MET

PEER

Liaison:

• Kantara
• eduPerson
• FIM4R
• GEANT

Joint work:

• eduGAIN policy
• GEANT Code of Conduct
• Mace-dir

Ops:

FOG list

• Steering Committee
• Sponsors
• Participants Agreement
• Workplan

Entity Categories

Risk

Address

Practicalities

and

REF 13-2: Entity Categories

tuff I haven't mentioned

PEER

REEP

An instance of PEER for Research and

Education Federations.

REF13-4: Understanding and improving metadata flow across federations

MET 2

Coming Soon!