A Middleware Unified Field Theory Identity Management / Directories Privileges / Groups Single Sign-On / Federation Enterprise Integration from network to application Michael R Gettes Internet2 August 2007 An interpretation of the original MACE mission
VO?
Inter-Enterprise Workgroup Collaborations not sexy
or C ollaborative O rganizations CO
Identity Groups Privileges Federated Access
and … Applications
Give COntrol To COmmunity Members
Integrate with Existing COmmon IT Infrastructures in Higher Education
Flexible Scalable Modular
COmponents S H I B B O L E T H LDAP-PC Signet Grouper LDAP Directory Identity Mgr Applications & Network COCO
stop talking start walking demo COmanage.internet2.edu
COmponents S H I B B O L E T H LDAP-PC Signet Grouper LDAP Directory Identity Mgr Applications & Network COCO
Comanage … is only a demonstration of the CO model a CO fits within a service delivery presentation
Stuff stored in Directories (everybody has one) Priv/Group data more accessible Allows for easy CO integration
Application Management App Access to data is managed by LDAP (initially) Identity data can be distributed by any desired mechanism in the future. SQL databases, feeds, message bus technologies.
Uses Shibboleth Federating technology Promotes InCOmmon Federation Might use other technologies OpenID?
Truth be told… LDAP-PC Large-Scale Performance and namespaces SIGNET Minor UI and Deployment GROUPER Some UI and Large-scale Performance SIGNET only immediate concern
Many COs on a single server ________ No local identity issued for external users to access CO services big win!
Signet/Grouper COmplexity A Service Opportunity? Middleware Service Provider (MSP) May also be locally deployed by HE institutions
Future… Protect CO by IdP can solve “IEEE problem”? Begin addressing issues of “attribute eCOnomy”
Network Layer? Why not? Integrate with Grids? Why not? Addresses VO scenarios? Why not?
V O VO? CO
done Talk amongst yourselves