Internet 2 Middleware Activities Progress Renee Wqodten Frost

Internet 2 Middleware Activities Progress Renee Wqodten Frost, Project Manager, Internet 2 Middleware Initiative I 2 Middleware Liaison, University of Michigan ………………. And an ensemble of hundreds

Activities Mace - RL “Bob” Morgan (Washington) Early Harvest / Early Adopters - Renee Frost (Michigan) LDAP Recipe - Michael Gettes (Georgetown) Edu. Person - Keith Hazelton (Wisconsin) Directory of Directories - Michael Gettes (Georgetown) Metadirectories - Keith Hazelton (Wisconsin) Shibboleth - Steven Carmody (Brown) PKI Labs - Dartmouth and Wisconsin HEPKI-TAG and PAG - Jim Jokl (Virginia) and Ken Klingenstein (Colorado) HEBCA - Mark Luker (EDUCAUSE) Medical Middleware - Rob Carter (Duke), Jack Buchanan (UT, Memphis) Opportunities - video, the GRID, K-12 CNI Spring 2001 Task Force Meeting

MACE (Middleware Architecture Committee for Education) Purpose: to provide advice, create experiments, foster standards, etc. on key technical issues for core middleware within higher ed Membership: Bob Morgan (UW) Chair Steven Carmody (Brown) Michael Gettes (Georgetown) Keith Hazelton (Wisconsin) Paul Hill (MIT) Jim Jokl (Virginia) Mark Poepping (CMU) David Wasley (U California) Von Welch (NCSA) CNI Spring 2001 Task Force Meeting

Early Harvest and Early Adopters Early harvest in the barn… http: //middleware. internet 2. edu/best-practices. html Early adopters aggressively doing deployments http: //middleware. internet 2. edu/earlyadopters Michigan Tech, U Maryland BC, Johns Hopkins, etc http: //www. colorado. edu/committees/Directory. Services/ CNI Spring 2001 Task Force Meeting

LDAP Recipe How to build and operate a directory in higher ed 1 Tsp. DIT planning 1 Tbsp Schema design 3 oz. configuration 1000 lbs of data Good details, such as tradeoffs/recommendations on indexing, how and when to replicate, etc. http: //www. georgetown. edu/giia/internet 2/ldap-recipe/ CNI Spring 2001 Task Force Meeting

LDAP Recipe Contents Directory Information Tree Schema Design Directory of Directories for Higher Education (Do. DHE) expectations Schema Design (continued) Schema: How to upgrade it? Password Management Bindings edu. Person attribute discussions Access Control Replication Name Population LDAP filter config file for white pages telephone. Number formatting CHANGELOG CNI Spring 2001 Task Force Meeting

edu. Person A directory objectclass intended to support inter-institutional applications Fills gaps in traditional directory schema For existing attributes, states good practices where known Specifies several new attributes and controlled vocabulary to use as values. Provides suggestions on how to assign values, but it is up to the institution to choose. Version 1. 0 now done; one or two revisions anticipated CNI Spring 2001 Task Force Meeting

Issues about Upper Class Attributes edu. Person inherits attributes from person, i. Net. Org. Person Some of those attributes need conventions about controlled vocabulary (e. g. telephones) Some of those attributes need ambiguity resolved via a consistent interpretation (e. g. email address) Some of the attributes need standards around indexing and search (e. g. compound surnames) Many of those attributes need access control and privacy decisions (e. g jpeg photo, email address, etc. ) CNI Spring 2001 Task Force Meeting

New edu. Person Attributes edu. Person. Affiliation edu. Person. Primary. Affiliation edu. Person. Org. DN edu. Person. Org. Unit. DN edu. Person. Principal. Name edu. Person. Nickname CNI Spring 2001 Task Force Meeting

edu. Person. Affiliation Multi-valued list of relationships an individual has with institution Controlled vocabulary includes: faculty, staff, student, alum, member, affiliate, employee Applications that use: Do. D, white pages CNI Spring 2001 Task Force Meeting

edu. Person. Primary. Affiliation Single-valued attribute that would be the status put on a name badge at a conference Controlled vocabulary includes: faculty, staff, student, alum, member, affiliate, employee Applications that use: Do. D, white pages CNI Spring 2001 Task Force Meeting

edu. Person. Principal. Name userid@securitydomain EPPN may look like an email address but it is used by different systems. One must be able to authenticate against the EPPN used in inter-realm authentication such as Shibboleth In some situations, it can be used for access control lists; if used, a site should understand the reassignment policy. CNI Spring 2001 Task Force Meeting

Next Steps edu. Person 1. 0 done, along with FAQ and letter to implementers Ties closely to LDAP recipe Version 2. 0 to include attributes for videoconferencing, additional collaboration factors, links to Grids, portals, etc. Check with web site for additional changes Participate: mace-dir@internet 2. edu CNI Spring 2001 Task Force Meeting

A Campus Directory Architecture Border directory Metadirectory Enterprise directory Departmental directories Dir DB Registries OS directories (MS, Novell, etc) Source systems CNI Spring 2001 Task Force Meeting

A Directory of Directories An experiment to build a combined directory search service To show the power of coordination Will highlight the inconsistencies between institutions Technical investigation of load and scaling issues, centralized and decentralized approaches Human interfaces issues - searching large name spaces with limits by substring, location, affiliation, etc. . . Two different experimental regimes to be tested • centralized indexing and repository with referrals • large-scale parallel searches with heuristics to constrain search space SUN donation of server and i. Planet license (6, 000 dn’s) Michael Gettes, Georgetown, is the project manager CNI Spring 2001 Task Force Meeting

Do. D Architecture Inputs to Do. DHE Inputs: Local Site View Central Deposit Service Do. D Config Directory Operation Search Operations • Search Drill Down from a list CNI Spring 2001 Task Force Meeting

Inputs Remote Data Sources LDAP Oracle Etc… Remote Site Directories Search Data Filtering & Submit to CDS Do. D Config Central Deposit Systems (CDS) CNI Spring 2001 Task Force Meeting

Inputs: Local Site View Submit final LDIF to CDS using authenticated POST via HTTPS. Local Data Source LDAP Generate LDIF Data Filter LDIF according to local policy. Generate new LDIF for submission. CDS CNI Spring 2001 Task Force Meeting D O D H E

Inputs: Why this way? Standardized input is LDIF • Could be XML but few products generate XML now (01/2001) Could use Metamerge Integrator as filter and submission mechanism Site always submits full dataset. No worry of reconciling. Easier site participation in the Do. DHE service. CDS handles reconciliation and controls data processing. Can provide feedback. CNI Spring 2001 Task Force Meeting

Metadirectories: Metamerge www. architech. no is now Metamerge Higher Education Contact for USA • Keith Hazelton, University of Wisconsin – Madison hazelton@doit. wisc. edu This product is available free of charge to Higher Ed in USA Source code will be in escrow. See Keith for further details. CNI Spring 2001 Task Force Meeting

Metamerge Features GUI development environment NOT a Meta-Directory, but a tool to build same functionality Various Languages: Java. Script, Java, Perl, Rexx, etc… Various Parsers: XML, LDIF, CSV, Script Interface, etc … for input and output Various Connectors: COMport, Files, HTTPserver, FTP, LDAP, JDBC, Oracle and more … The product is ALL Java CNI Spring 2001 Task Force Meeting

This begs the following … If you were given both this Metamerge LDIFTransformer and a Perl script that is the basis for the same functionality – each need to be customized for local purposes – which appears more attractive to you? Answer: from querying various institutions on this question the common response, nearly 100%, is that use of Metamerge is good, interesting and yields other possibilities not likely with just a Perl script. So, the Do. DHE will progress assuming Metamerge. If your institution would like to do something different, then you are welcome to do so. Hopefully a common solution will have benefits beyond a custom solution. CNI Spring 2001 Task Force Meeting

Shibboleth A word which was made the criterion by which to distinguish the Ephraimites from the Gileadites. The Ephraimites, not being able to pronounce sh, called the word sibboleth. See --Judges xii. Hence, the criterion, test, or watchword of a party; a party cry or pet phrase. - Webster's Revised Unabridged Dictionary (1913): CNI Spring 2001 Task Force Meeting

Shibboleth An initiative to analyze and develop mechanisms(architectures, frameworks, protocols and implementations) for interinstitutional web access control Facilitated by Mace (a committee of leading higher ed IT architects) and Internet 2 “Authenticate locally, act globally” the Shibboleth shibboleth Oriented towards privacy and complements corporate standards efforts Open solution http: //middleware. internet 2. edu/shibboleth Vendor participation - IBM et al CNI Spring 2001 Task Force Meeting

Isn’t This What PKI Does? PKI does this and a whole lot more; as a consequence, PKI does very little right now End-to-end PKI fits the Shibboleth model, but other forms of authentication do as well Uses a lightweight certificate approach for inter-institutional communications - uses the parts of PKI that work today (server side certs) and avoids the parts of PKI that don’t work today (eg client certs). Allows campuses to use other forms of authentication locally May actually have benefits over the end-user to target-site direct interactions. . . CNI Spring 2001 Task Force Meeting

Related Work Previous DLF work http: //www. clir. org/diglib/presentations/cnis 99/sld 001. htm OASIS Technical Committee (vendor activity, kicked off 1/2001) http: //www. oasisopen. org/committees/security/index. shtml http: //lists. oasis-open. org/archives/security-services/ UK - Athens and Sparta projects http: //www. jisc. ac. uk/pub 00/sparta_disc. html Spain - rediris project http: //www. rediris. es/app/papi/index. en. html CNI Spring 2001 Task Force Meeting

Assumptions “authenticate locally, act globally” the Shibboleth shibboleth Leverage vendor and standards activity wherever possible Disturb as little of the existing campus infrastructure as possible Work with common, minimal authorization systems (eg htaccess) Encourage good campus behaviors Learn through doing Create a marketplace and reference implementations We will not be another dead guppy Protect Personal Privacy! CNI Spring 2001 Task Force Meeting

Development Process Scenarios leading to requirements Establish model architectures for common services and scenario-specific services Develop service and protocol requirements Identify service options/begin protocol development Produce open implementations of missing service components; provide external services as needed CNI Spring 2001 Task Force Meeting

Model Local Authentication Local Entity Willing to Create and Sign Entitlement • • Set of assertions about the user (Attribute/value pairs) User has control over disclosure Identity optional “active member of community”, “Associated with Course XYZ” Target responsible for Authorization • Rules engine • Matches contents of entitlements against ruleset associated with target object Cross Domain Trust • Previously created between origin and target • Perhaps there is a contract (information providers. . ) CNI Spring 2001 Task Force Meeting

Shibboleth Architecture Concepts - High Level Pass content if user is allowed Authorization Phase Target Web Server Browser Authentication Phase First Access - Unauthenticated Origin Site Target Site CNI Spring 2001 Task Force Meeting

Shibboleth Architecture Concepts #1 (managing trust) Club Shib Server (holds certs and contracts) Attribute Server Shib htaccess plugin Target Web Server Browser Origin Site Target Site CNI Spring 2001 Task Force Meeting

Campus and Resource Requirements To Participate in Shibboleth, a site must have: • Campus-wide authentication service • Campus-wide identifier space (EPPN) • Implementation of Edu. Person objectclass • Ability to generate attributes (eg “active member of the community”) CNI Spring 2001 Task Force Meeting

Issues Personal Privacy (reasonable expectation, laws) Relation to local weblogin (Single Signon) Portals Use of Shibboleth framework by services beyond the web Grid resources and users CNI Spring 2001 Task Force Meeting

Internals of the Shibboleth Model: Functions and Standards There are component services that are assumed to exist already on campuses There are new functional services that must be implemented There are new protocols that must be developed There are data and metadata definitions that must be standardized. CNI Spring 2001 Task Force Meeting

Internals of the Shibboleth Model: Services, standards, protocols Identifier privacy engine Web access control service Where from service OASIS XML Standard Credential Factory Local authentication service Institutional shib key distribution service Inter-realm information exchange protocols for authentication and authorization Web SSO service Local Shibboleth control point Local attribute server CNI Spring 2001 Task Force Meeting

Project Status/Next Steps Requirements and Scenarios document nearly finished IBM and Mace-Shibboleth are refining architecture and evaluating issues IBM intends to develop an Apache web module Internet 2 intends to develop supporting materials (installation, documentation, etc) and web tools (for htaccess construction, filter and access control, remote resource attribute discovery). Technical design complete - April, 2001 Coding. . . Pilot site start-up - Aug, 2001 Public demo- Internet 2 Fall Member Meeting 2001 CNI Spring 2001 Task Force Meeting

Shibboleth, edu. Person, and Middleware Inputs & Outputs everything else Licensed Resources Grids OKI Embedded App Security JA-SIG & u. Portal Inter-realm calendaring Shibboleth, edu. Person, Affiliated Dirs, etc. Campus web sso Enterprise Directory Enterprise Authentication futures Enterprise Auth. Z Legacy Systems CNI Spring 2001 Task Force Meeting

Internet 2 PKI Labs At Dartmouth and Wisconsin in computer science departments and IT organizations Doing the deep research - two to five years out Policy languages, path construction, attribute certificates, etc. National Advisory Board of leading academic and corporate PKI experts provides direction Catalyzed by startup funding from ATT CNI Spring 2001 Task Force Meeting

HEPKI-TAG Chaired by Jim Jokl, Virginia Certificate profiles • survey of existing uses • development of standard presentation • identity cert standard recommendation Mobility options – IETF SACRED scenarios Public domain software alternatives CNI Spring 2001 Task Force Meeting

HEPKI-PAG David Wasley, UCOP, prime mover Draft certificate policy for a campus HEBCA certificate policy FERPA State Legislatures Gartner Group Decision Maker software CNI Spring 2001 Task Force Meeting

Medical Middleware Unique requirements - HIPAA, disparate relationships, extended community, etc. Unique demands - 7 x 24, visibility PKI seen as a key tool Mace-med recently formed to explore the issues CNI Spring 2001 Task Force Meeting

The complex challenges of academic medical middleware Intra-realm issues - multiple vendors, proprietary systems, evolving regulations Enterprise issues - security, directories, authorization; balance of institutional and medical enterprises Inter-realm issues - standards, gateways, common operational processes and policies, performance Multiple communities of interest - institutional, medical center, affiliated hospitals, state and federal regulatory and certification organizations, insurance companies, medical researchers, etc. CNI Spring 2001 Task Force Meeting

The applications view of medical upperware Client (in this scenario) Server (in this scenario) VA Clinical System Do. D Clinical System Request lab data, This Soldier, this time frame Who’s asking? What role? What is need to know? Resource Access Decision (RAD) Who is this person? Who knows this person? Person Identification Service (PIDS) Where is lab info on this. Convert to server’s terms person? Health Information Locator Service (HILS) Terminology Query Service (TQS) outbound Request observation Clinical Observation Access Service (COAS) CNI Spring 2001 Task Force Meeting

The enterprise architect view of medical middleware Medical Administrative Systems Research Systems Hospital Administrative Systems Internet App dir LAN dir Institutional Student Financial Personnel Systems Person registry Border Directory Enterprise directory Authentication Services Peer institutions Corporate collaborators PKI Authorization Services Federal State Gov’ts CNI Spring 2001 Task Force Meeting

Video A variety of tools - vic/vat, H. 323, MPEG 2, HDTV Point-to-point and MCU options H. 323 desktop video within reach at physical layer Lacks identifiers and authentication EPPN and Shibboleth-type flow could address CNI Spring 2001 Task Force Meeting

K-12 The killer app may be a spreadsheet and resource discovery Directories to locate information Directories to store experiments Technology isn’t enough CNI Spring 2001 Task Force Meeting

More information Early Harvest / Early Adopters: http: //middleware. internet 2. edu/earlyadopters/ Mace: middleware. internet 2. edu LDAP Recipe: http: //www. georgetown. edu/giia/internet 2/ldaprecipe/ Edu. Person: www. educause. edu/eduperson Directory of Directories: middleware. internet 2. edu/dodhe Shibboleth: middleware. internet 2. edu/shibboleth HEPKI-TAG: www. educause. edu/hepki HEPKI-PAG: www. educause. edu/hepki Medical Middleware: web site to follow Opportunities: video, the GRID, K-12 CNI Spring 2001 Task Force Meeting