Connect. Communicate. Collaborate The eduGAIN Way Diego R. Lopez - RedIRIS

Connect. Communicate. Collaborate As Federations Grow The risk of dying of success –Do we really need to go on selling the federated idea? Different communities, different needs –Not even talking about international collaboration –Different (but mostly alike) solutions –Grids and libraries as current examples –And many to come: Governments, professional associations, commercial operators,… Don’t hold your breath waiting for the Real And Only Global Federation

Connect. Communicate. Collaborate Confederations Federate Federations Same federating principles applied to federations themselves –Own policies and technologies are locally applied Independent management –Identity and authentication-authorization must be properly handled by the participating federations Commonly agreed policy –Linking individual federation policies –Coarser than them Trust fabric entangling participants –Whitout affecting each federation’s fabric –E2E trust must be dynamically built

Connect. Communicate. Collaborate Applying Confederation Concepts in eduGAIN An eduGAIN confederation is a loosely-coupled set of cooperating federations –That handle identity management, authentication and authorization using their own policies Trust between any two participants in different federations is dynamically established –Members of a participant federation do not know in advance about members in the other federations Syntax and semantics are adapted to a common language –Through an abstract service definition

Connect. Communicate. Collaborate The eduGAIN Model Connect. Communicate. Collaborate Id Repository(ies) Resource(s) MDS R-FPP Metadata Publish R-BE Metadata Query AA Interaction H-FPP Metadata Publish H-BE AA Interaction AA Interaction

Connect. Communicate. Collaborate An Adaptable Model From centralized structures... Connect. Communicate. Collaborate MDS FPP BE FPP BE SP IdP SP

Connect. Communicate. Collaborate An Adaptable Model...to fully E2E ones... Connect. Communicate. Collaborate MDS SP BE IdP BE SP BE SP BE SP BE SP BE IdP BE IdP BE IdP BE SP BE IdP BE IdP BE IdP BE SP BE SP BE SP BE

Connect. Communicate. Collaborate An Adaptable Model...including any mix of them Connect. Communicate. Collaborate MDS SP BE IdP BE IdP BE IdP BE SP BE SP BE SP BE FPP BE SP IdP BE FPP

Connect. Communicate. Collaborate A General Model for eduGAIN Interactions Connect. Communicate. Collaborate RequesterResponder Id Repository Resource TLS Channel(s) MDS TLS Channel ?cid=someURN <EntityDescriptor... entityID= ”urn:geant2:..:responder">... <SingleSignOnService... Location= “ />... <samlp:Request... RequestID=”e70c3e9e6…” IssueInstant=“ …”>... <samlp:Response... ResponseID=”092e50a08…” InResponseTo=“e70c3e9e…”>...  urn:geant2:...:responder urn:geant2:...:requester 

Connect. Communicate. Collaborate A Layered Model for Implementation Connect. Communicate. Collaborate Component logic eduGAINBase + eduGAINVal + eduGAINMeta SAML toolkit (OpenSAML) SOAP/TLS/XMLSig libraries eduGAINBase Profile Access

Connect. Communicate. Collaborate The eduGAIN APIs: Trust Evaluation Connect. Communicate. Collaborate eduGAINVal Configuration Key Store Trust Store Is this trust material (cert/signature) valid? Does it correspond to component X*? Valid/not valid Corresponds to component X Sign this piece of XML Signature Which trust material to use for connecting Trust material

Connect. Communicate. Collaborate The eduGAIN APIs: Metadata Access Connect. Communicate. Collaborate eduGAINMeta Configuration Publish these metadata through MDS server Component metadata Give me metadata about this part of eduGAIN Metadata eduGAINVal Publishing result Which component(s) can be queried to retrieve data about someone with these Home Locators?

Connect. Communicate. Collaborate The eduGAIN APIs: Abstract Service Connect. Communicate. Collaborate eduGAINBase Configuration Create/manipulate an abstract service object Abstract service object or Protocol element Send ASO: (AuthN/Attr/AuthR) request (Vanilla profile) Corresponding ASO responseAbstract service object Transform these abstract service object to/from wire protocol eduGAINMeta eduGAINVal

Connect. Communicate. Collaborate The eduGAIN APIs: Profile Access Connect. Communicate. Collaborate eduGAIN Profile API Configuration Is this AuthN/Attr material valid? Valid/not valid Provide data from the requester Data Create/modify a security token Token eduGAINBase eduGAINMeta eduGAINVal Is this request authorized? Authorization response

Connect. Communicate. Collaborate eduGAIN Profiles Oriented to –Enable direct federation interaction –Enable services in a confederated environment Four profiles discussed so far –WebSSO (Shibboleth browser/POST) –AC (automated cilent: no human interaction) –UbC (user behind non-Web client: use of SASL-CA) –WE (WebSSO enhanced client: delegation) Others envisaged –Extended Web SSO (allowing the send of POST data) –eduGAIN usage from roaming clients (DAMe) Based on SAML 1.1 –Mapping to SAML 2.0 profiles along the transition period

Connect. Communicate. Collaborate The WebSSO Profile Connect. Communicate. Collaborate

The AC Profile Connect. Communicate. Collaborate

The UbC Profile Connect. Communicate. Collaborate

The WE Profile Connect. Communicate. Collaborate

The Paved Way The first eduGAIN enabled resource is already available – –As a result of the implementation of the WebSSO profile Prototypes for –The MDS –The component ID registry –The PKI components eduGAIN base APIs available at the GN2 SVN server Cookbook and reference material

Connect. Communicate. Collaborate The Road Ahead Implementing the rest of initial profiles –Direct collaboration with initial user activities –And initial liaisons with some others Migration to SAML2 –Plans to align as much as possible with Shibboleth 2 Building stable support services –Many component IDs foreseen –Web-based and extensible PKI services Keeping coolness –CardSpace –OpenID And policy!