1. Supporting Institutions Towards a Shibbolized Infrastructure
John Paschoud
SECURe Project, LSE Library
JISC MwI meeting, 05-May-2004

2. [contents] [recap] Issues for Institutions Scoping the problem
Assembling resources
A pilot support service
Monitoring progress
Exit strategy
JISC MwI meeting, 05-May-2004

3. Shibboleth Status V1.2 available May 2004
Relatively straightforward to install, provided there is good web services understanding and middleware infrastructure (authentication, directories, webISO, etc.).
Target - works with Apache and IIS targets; Java origins.
V2.0 likely to include portal support (incl PERSEUS development of uPortal toolkit)
Work underway on some of the essential management tools such as attribute release managers, target resource management, etc.
Can take between 3 hours and 3 years to install
How much infrastructure (core middleware) do you already have?
provided there is good web services understanding and middleware infrastructure (authentication, directories, webISO, etc)
JISC MwI meeting, 05-May-2004

4. Implications for UK infrastructure
No dependency on a VERY LARGE centralised database
Need for implementation of a national WAYF service
better than current end-user interface model
(new WAYF options being developed)
Lower shared costs?
(but greater costs devolved to institutions)
JISC MwI meeting, 05-May-2004

5. Benefits to Institutions
Much easier Inter-Domain Integration
With other campuses
With off-campus vendor systems
Integration with other campus systems, intradomain
LMS
Med School……
Ability to manage access control at a fine-grained level
Allows personalization, without releasing identity
Implement Shibboleth once…
And then just manage attributes that are released to new targets
JISC MwI meeting, 05-May-2004

6. Implications for Institutions
Less duplicated end-user admin than with Athens
(similar to AthensDA)
Need for agreement on role attributes (eduPerson) for end-user description
Many don’t yet have standards-based supporting services (SSO, enterprise directories)
(but new costs would largely replace & improve, rather than add-to, existing ad-hoc AM mechanisms)
JISC MwI meeting, 05-May-2004

7. Shibboleth Architecture (still photo, no moving parts)
JISC MwI meeting, 05-May-2004

8. [LSE/SECURe AM infrastructure]
JISC MwI meeting, 05-May-2004

9. Scoping the need HE support: FE support:
Documents, Helpdesk, Installation support
Existing services (OMII etc)
FE support:
Managed services?
Existing support services (InfoNet etc)
Survey of directory management policies & technologies used
JISC MwI meeting, 05-May-2004

10. Assembling resources
What can (and can’t) be re-used from US CAMP programme?
Outputs from AAA projects (SECURe etc)
Models & materials from other European adopters (SWITCH etc)
JISC MwI meeting, 05-May-2004

11. A pilot support service
Costed & planned by end AY 2004/05
Operating for AY 2005/06 only
Opportunity to try different approaches with early-adopter institutions
Close working with DSPs
JISC MwI meeting, 05-May-2004

12. Monitoring progress
Continuous self-evaluation & feedback from early-adopters
Establishing national measures of Shibbolization
Refining estimates of resources and timescale for full transition to new MwI
JISC MwI meeting, 05-May-2004

13. Exit strategy
Assessment of long-term support need – evidence from HE & FE
Recommendations for long-term support service, incl cost-benefit case
Outline plan for service
Resources to be used by service
JISC MwI meeting, 05-May-2004