+ All Categories
Home > Documents > ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to...

~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to...

Date post: 17-Jan-2018
Category:
Upload: amanda-palmer
View: 216 times
Download: 0 times
Share this document with a friend
Description:
What do we want? Inter-Enterprise Workgroup Collaborations not sexy
21
~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant messaging, voice conferencing services 4.Doesn’t want to be in the identity issuance business for external collaborators 5.Need to allow external + internal collaborators to use A Short description of Internet
Transcript
Page 1: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

~60 staff

1. Collaborators around the world2. Supports communities of collaborators

external to Internet23. Community uses wiki, mailing lists, instant

messaging, voice conferencing services4. Doesn’t want to be in the identity issuance

business for external collaborators5. Need to allow external + internal

collaborators to use same service instances

A Short description of Internet2

Page 2: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

A MiddlewareUnified Field Theory

Identity Management / Directories Privileges / Groups

Single Sign-On / FederationDiagnostics

Enterprise Integration

from network to application Michael R GettesInternet2

October 2007An interpretation of the original MACE mission

Page 3: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

What do we want?

Inter-EnterpriseWorkgroup

Collaborations

not sexy

Page 4: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

or

Collaborative

Organizations

CO

Page 5: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

Identity

Groups

Privileges

Federated Access

Page 6: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

and …

Applications

“It’s the App stupid!”

Page 7: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

Give

COntrol

To

COmmunity Members

Page 8: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

Integrate withExisting

COmmonIT Infrastructures

in

Higher Education

Page 9: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

FlexibleScalableModular

Page 10: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

COmponents

S H I B B O L E T H

LDAP-PC

Signet Grouper

LDAPDirectory

IdentityMgr

Applications & Network

CO

Page 11: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

stop talkingstart walking

demo

COmanage.internet2.edu

Page 12: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

COmponents

S H I B B O L E T HS H I B B O L E T H

LDAP-PC

Signet Grouper

LDAPDirectory

IdentityMgr

Applications & Network

CO

Page 13: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

Comanage …

is only a demonstration ofthe CO model

a CO fits within a service

delivery strategy

Page 14: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

Application Management

App Access to data ismanaged by LDAP (initially)

Identity data can be distributed by any desired mechanism in the future. SQL databases, feeds, message bus technologies.

Page 15: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

Many COson a single server

(if you wanna do that)

Grouper/Signet/LDAP-PC

Identity Mgr

Grouper/Signet/LDAP-PCGrouper/Signet/LDAP-PCGrouper/Signet/LDAP-PCGrouper/Signet/LDAP-PCGrouper/Signet/LDAP-PCGrouper/Signet/LDAP-PCGrouper/Signet/LDAP-PCGrouper/Signet/LDAP-PC

LDAP

Application setApplication setApplication setApplication setApplication setApplication set

Page 16: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

No local identity issued for external users to access

CO servicesbig win!

O=University,c=USou=People (this is where 50K fac/staff/stu might reside)ou=CO (external identities for CO go here)ou=Groups (a place to store groups for all)

Example directory tree for CO environment

Applications pointed here for identitiesyields the union of internal and external

Page 17: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

Future…Begin addressing issues of “attribute

eCOnomy”Protect CO by Identity Provider…

can solve “IEEE problem”?

Web site wants to

know:Are you a

member of IEEE?

MyUniversity

IEEE-COThis org hasmembershipdata but doesnot manageidentity - a COwith onlyexternal users.

User

HomeIdentity Provider

Page 18: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

Diagnostics

Lifting up shib log filesand making EDDY deposits

Creating a unified and federated view of diag data•Network data: flows, snort, snmp•System stats: cpu, i/o, mem, etc…•Infrastructure: shib, ldap, authN, etc…•Application: http, confluence, sympa, calendar

etc, etc, etc…

http://web.cmu.edu/eddy

Page 19: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

Network Layer?Why not?

Integrate with Grids?Why not?

Addresses VO scenarios?Why not?

Page 20: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

VOVO?CO

Page 21: ~60 staff 1.Collaborators around the world 2.Supports communities of collaborators external to Internet2 3.Community uses wiki, mailing lists, instant.

Make your opinion known…

Should Internet2 use COmanage for service delivery?

Rick Summerhill [email protected] Fremon [email protected]

and [email protected] [email protected]


Recommended