1 / 46

Network Operations

OpenConext Workshop Down-Under. Network Operations. Session 1: Overview. Enabling Federated Team Management, Group-Aware SPs, and SP Shop-Fronts Neil Witheridge, AARNet Authentication & Authorisation Services Technical Manager 25 th October 2013. Overview. Session 1: Overview - Topics.

reuel
Download Presentation

Network Operations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OpenConext WorkshopDown-Under Network Operations Session 1: Overview Enabling Federated Team Management, Group-Aware SPs, and SP Shop-Fronts Neil Witheridge, AARNetAuthentication & Authorisation Services Technical Manager25th October 2013

  2. Overview Session 1: Overview - Topics Session Topics: • Federated Authentication & Authorisation Background • OpenConext Features(SP Shopfront, Group/Team mgnt& Group info retrieval) • Architecture & Components(Demo clean installed OpenConext) • SAML Proxy: IdP and SP Integration(Demo integrated IdP and SP) • Group/Team Management(Demo Team Creation & Management) • Group Proxy: Group Provider Integration(Demo API Playground)

  3. Overview Session 1: Overview - Topics Session Topics cont’d • Virtual Organisations & VO-based Authorisation(Demo VOs & AuthZ) • OpenSocial Container, Portal & Gadget Integration(Demo Shindig OpenSocial Container, Rave Portal & Etherpad gadget) • Security, Sustainability & Usability • OpenConext Roadmap • Session Wrap-up Non-third-party-sourced content is under the Creative Commons “Attribution 3.0 Unported” license. This means that you are permitted to freely copy, distribute, display, present, or perform material on the wiki, and create derivative works from it, for either commercial or non-commercial purposes.

  4. Overview Federated Authentication & Authorisation Background

  5. Overview Federated Authentication • SAML Federated Identity & Access ‘state of the art’ • Service Providers trust Identity Providers & vice versa (via SAML metadata) • SPs requests user attributes from the user’s IdP (info stored in institution’s identity store) • IdP delivers according to Attribute Release Policy (ARP), with optional user consent • E.g. AAF • Metadata • Policy • Info • WAYF

  6. Overview Authorisation Post Federated AuthN • Importance of group-based access for HE&R services • Research Team access to federated services • VOs for Grid Services • Service licensing, restricted access to commercially sensitive info • User information used by service for authorisation decision • IdP user attributes • IdP authoritative & owned, directory schema -> namespace • Team-attributes (Research Teams, Virtual Organisations) • Team authoritative & owned namespace (URN), bilateral agreement with services • urn:collab:group:biolabs:au:genome-team • Authorisation Rights (e.g. populated in eduPersonEntitlement) • Service authoritative & owned namespace (URN), delegates authority to issue • urn:service-x:entitlement:foo

  7. Overview Group-management Systems Source: http://www.its.hku.hk/services/research/grid/egee/userguide Source: http://www.internet2.edu/products-services/trust-identity-middleware/grouper/ Source: https://spaces.internet2.edu/display/COmanage/Home Source: http://www.switch.ch/aai/support/presentations/installfest-2008/D2-P3-GMT.pdf Source: http://www.eresearch.edu.au/docs/280607/James_Dalziel_Alan_Lin_Neil_Witheridge.pdf Source: SURFnet Source: SURFnet Source: SURFnet http://www.youtube.com/watch?v=kUpn568NSl0&feature=player_embedded

  8. Overview OpenConext Features

  9. Overview SAMLFed, IdP, SP Integration • Federated authentication of users

  10. Overview SAML Proxy Benefits • OpenConext Engine as an IdP/SP Proxy • Hub&Spoke -> centralised admin • Potential for attribute aggregation • Enables Services Shopfront

  11. Overview Group Information Retrieval • Authenticated user group information from “Group Providers” • Internal Group Provider “Grouper” + External Group Providers • Registration of Group Providers = shared credentials

  12. Overview Group/Team Management • Types of Group Providers supported by OpenConext: • Grouper • OpenSocial • Group Management via “Teams” (interface to “Grouper”) • Need trust in both Group management side (cf. IdP & institutional idm) and mechanism for group information retrieval (cf. attribute resolver) • Internet2’s Grouper is comprehensive group management solution • Hierarchical groups, stems • Advanced delegation of authority to administer • “stem”: string that forms the leading part of a Group's name Source: http://www.internet2.edu/products-services/trust-identity-middleware/grouper/

  13. Overview OpenConext Architecture and Components

  14. Overview OpenConext Architecture Source: http://www.internet2.edu/products-services/trust-identity-middleware/grouper/

  15. Overview OpenConext Components • Application components making up OpenConext Grouper JANUS Java MockGroup Provider API Playground

  16. Overview OpenConext Installation • OpenConext Repository https://github.com/OpenConext • Downloading OpenConext from Githubgit clone https://github.com/OpenConext/OpenConext-vm.gitorcurl https://codeload.github.com/OpenConext/OpenConext-vm/tar.gz/master • Easy OpenConext installation by running installation scripts • Installation and setup will be covered in next session • Mujina IdP • Installed and pre-configured as IdP in OpenConext • convenient ‘test’ and ‘bootstrap’ IdP’ • provides default “admin” user • REST interface provided to create users e.g. “addjane”

  17. Overview Installed Components • ServiceRegistry • OpenConext admin user management • SAML Proxy configuration • Adding connections (IdP and SP) • Manage • OpenConext usage, access to Engine metadata • Adding Group Providers (also to configure test External Group Provider) • Creating VOs (VO-based authZ described later) • Other tools • Teams (creation and management of Teams) (and Grouper native UI) • API Playground (experiment with Group Info retrieval via “API” component) • Profile (basic identity management)

  18. Overview SAML Proxy: IdP and SP Integration

  19. Overview SAML-Proxy functionality • Engine proxies trusted SPs to trusted IdPs & vice versa • Trusted IdPs metadata provisioned in Engine SP • Engine IdP metadata provisioned in Trusted SPs

  20. Overview Integration with SAML Fed • OpenConext in the national federation • Registered as single SP (Engine) • Federation IdPs release attributes to OpenConext Engine • Proxy functionality -> “SP shopfront” or “Super SP”

  21. Overview Attribute Release Policy (ARP) • OpenConext Engine deployed as SPin the National SAML Fed • Engine SP SAML metadata provisioned in Nat Fed IdPs (& vice versa) • OpenConext SPs provisioned with Engine IdP SAML metadata (& vice versa) • Attribute requirements for Engine determine Nat Fed IdPs’ ARP • Attribute req’s for OpenConext SPs determine OpenConext IdP ARP • Only att’s received by Engine SP are available for release by Engine IdP • OpenConext SP requirements configured in Service Registry

  22. Overview SAML Proxy Technology • OpenConext Engine (Corto) & Service Registry (JANUS) • Reuse of mature technology for SAML proxying, metadata admin • SURFnet responsible for JANUS development • Cortohttps://sites.google.com/site/cortopages/ • JANUShttp://code.google.com/p/janus-ssp/ Source: https://code.google.com/p/janus-ssp/ Source: https://sites.google.com/site/cortopages/

  23. Overview SAML Proxy: Power & Flexibility “IdP A” a member of Nat SAML Fed butnot trusting/trusted by OpenConext(i.e. users can’t access “SP 1”, “SP-2”, “SP 3”) “IdP 1”& “IdP 2” not members of Nat Fed but trusted by OpenConext(i.e. users can’t access “SP A” or “SP B”)

  24. Overview Group/Team Management

  25. Overview Group/Team Management • Groups/Teams • Groups=Teams in OpenConext • Team types: private, public • Group Providers • Source of user group information (cf IdP for SAML federation) • Built-in Group Provider: Internet2’s “Grouper” • OpenConext groups/teams are flat • External Group Providers can be integrated • Types of Group Provider: Grouper, OpenSocial • OpenConext “Teams” service, a GUI for Grouper • Provision of GUI for External Group Providers ? Source: http://www.internet2.edu/products-services/trust-identity-middleware/grouper/

  26. Overview Team creation and admin • “Teams” provides for secure team creation and administration • Delegation of responsibilities for team administration • User role requirements for team creation • Email workflow • User added to team at manager’s invitation • User added to team at user’s request • Adding Groups to Teams • tbd • Using the Grouper GUI directly • Significance of ‘stem’

  27. Overview Group Proxy Group Provider Integration ( for Group Information Retrieval)

  28. Overview Group Proxy Functionality • “API” component acts as Proxy to Group Providers for SPs

  29. Overview VOOT Protocol • From SP perspective, requests are issued via VOOT protocol • Retrieval of group and person information • Standardised REST API based on OpenSocial Social API • Subset of OpenSocial + {voot_membership_role} attributes • Supported Requests: • Information about authenticated user /people/@me • List of groups the user is a member of /groups/@me • List of people that are members of the user’s group /people/@me/<groupId> • OAuth 2.0 and OAuth 1.0a (for legacy SPs) authentication supported

  30. Overview VOOT Request/Response e.g. GET /groups/@me?sortBy=title HTTP/1.1 HTTP/1.1 200 OKContent-Type: application/json{ "entry": [ { "description": "Group containing employees.", "id": "employees", "title": "Employees", "voot_membership_role": "admin" }, { "description": "Group containing everyone at this institute.", "id": "members", "title": "Members", "voot_membership_role": "member" } ], "itemsPerPage": 2, "startIndex": "0", "totalResults": 2 } Source: http://www.internet2.edu/products-services/trust-identity-middleware/grouper/

  31. OAuth Authentication • OAuth v2.0, Authorisation Code Grant Source (reproduced in): http://www.bubblecode.net/en/2013/03/10/understanding-oauth2/

  32. Overview API Playground • OpenConext provides an ‘API playground’ for testing OAuth/VOOT calls • OAuth actors • Resource, Resource Owner, Resource Server, Client, Authorisation Server • OAuth security • Client Registration with Authorisation Server (consumer key, secret) • Reliance on TLS (i.e. use of https) in requests to service end-points • API Playground OAuth protocols supported • Version 1.0a 3-legged, 2-legged • Version 2.0 Authorization Code Grant, Implicit Grant • API Playground workflow • OAuth Settings • Authorisation Request • API Request (changing the API Request to explore different VOOT requests)

  33. Overview Putting it together: SAML + Group Proxy

  34. Overview Virtual Organisations and VO-based Authorisation

  35. Overview VO’s and VO-based AuthZ • In OpenConext, a Virtual Organisation is an group aggregator • Defined in terms of groups, IdPs and stems • Creating a VO • “Manage” component provides for VO creation • Types of VO: group(s), IdP(s), group(s)+IdP(s), stem • Access to resources based on VO membership • Authorisation built into OpenConext engine • VO-based authorisation by virtue of Engine SAML IdP metadata • Generate Engine IdP SAML metadata with VO suffix vo:<voName> • Provision protected SP with Engine IdP metadata • Only members of the VO (Groups, IdPs, stem) can access the service

  36. Overview VO-Based Authorisation

  37. Overview OpenSocial Container, Portal and Gadget integration

  38. Overview JISC Conext / Jacson • Uptake of OpenConext by JISC • Development of JISC Conext / Jacson (initially for JISCmail) • Integration of OpenSocial Container & Portal in OpenConext • Initially intended to be an integral part of OpenConext • OpenSocial Container – Apache Shindig • OpenSocial Portal – Apache Rave • OpenSocial Gadgets – e.g. Etherpad • Federated Authentication and Group Information retrieval • Uptake of OpenSocial technology. • Key value of OpenSocial Portal infrastructure such as “Jacson” • Potential for Australian HE&R Service Providers?

  39. Overview Security, Sustainability and Ease-of Use

  40. Overview OpenConext Security • OpenConext Security Mechanisms • SAML Proxy related, Group Proxy related (OpenSocial API) • OpenConext Security • Analysis undertaken of SURFconext components by 3rd party • Australian HE&R focus on Group Information Retrieval • VOOT/OAuth security • reliance on TLS • Considerable work on Oauth Security undertaken • http://tools.ietf.org/html/draft-ietf-oauth-v2-threatmodel-01 • Security Analysis of Double redirection protocols http://pomcor.com/techreports/DoubleRedirection.pdf

  41. Overview OpenConext Sustainability • Continuing use for The Netherland’s National SAML Federation • Global uptake & collaboration (e.g. in deploying, documenting) JISC Internet2 Source: http://conext.jiscconext.org.uk/cgi-bin/greeting?instanceID=1 Source: https://spaces.internet2.edu/download/attachments/10732/2012-COmanage-info-rev.pdf

  42. Overview Ease of Use • Deployment • Open Source, supported, growing development & user community, maillists • Focus on documentation, ease of installation • Development • OpenSocial / OAuth Client libraries available for most languages • Java (e.g. Scribe) • PHP (e.g. zend_oauth) • Python (e.g. rauth) • Workshops & conferences • Active topic at technical conferences • Workshops being created & delivered

  43. Overview OpenConext Roadmap

  44. Overview OpenConext Roadmap • Niels van Dijk to describe current priorities and future plan forOpenConext development • Also (depending on time) report on • Global Uptake • Documentation effort • Commitment of SURFnet to support for global uptake • Keeping informed and contributing to development

  45. Overview Wrapping Up, Questions ? neil.witheridge@aarnet.edu.au niels.vandijk@surfnet.nl

  46. Overview Preparation for Session 2 • Session 2 to go into technical detail, building on Session 1 • SP development work will be undertaken during afternoon sessions • Preparation for Session 2: • Preparation section • Confirm connectivity • Virtual Machines • Assigned to participants – add initials on VM list to reserve • Note IP address, domain name • Username and password on whiteboard • Access via SSH

More Related