Federated Access Management: the Business Case

2,491 views
2,323 views

Published on

This presentation sets out a business case template to be used by institutions considering adopting federated access management

Published in: Business, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,491
On SlideShare
0
From Embeds
0
Number of Embeds
59
Actions
Shares
0
Downloads
211
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Federated Access Management: the Business Case

  1. 1. Connecting People to Resources Federated Access: Building the Business Case Nicole Harris Programme Manager
  2. 2. The JISC Roadmap
  3. 3. Reviewing Readiness How many institutions will adopt federated access by July 2008? (FE figures: Scotland, Wales and Northern Ireland only)
  4. 4. Federated Access: Developing a Business Case Writing the Business Case
  5. 5. JISC InfoNet Toolkits
  6. 6. JISC InfoNet: Example Business Case Example of Electronic and Document Management System Business Case Development
  7. 7. NMI-EDIT Enterprise Directory Implementation Roadmap
  8. 8. Alpha University Business Case
  9. 9. NMI Enterprise Authentication Roadmap
  10. 10. Elements of a Business Case <ul><li>Strategic Fit: making the strategic case. </li></ul><ul><ul><li>Inputs and background, institutional strategy drivers (information strategy), other strategic drivers (external), timing implications, critical success factors. </li></ul></ul><ul><li>Options Appraisal: the economic case. </li></ul><ul><ul><li>Including costs and benefits analysis for each option. </li></ul></ul><ul><li>Commercial aspects: the financial case (1). </li></ul><ul><ul><li>Looks specifically at outsourcing and procurement issues. </li></ul></ul><ul><li>Affordability: the financial case (2). </li></ul><ul><ul><li>Funds available for project (implementation) and ongoing running. </li></ul></ul><ul><li>Achievability: the project management case. </li></ul><ul><ul><li>Can this be achieved within the organisation’s current capability and capacity? </li></ul></ul>
  11. 11. Federated Access: Developing a Business Case The Strategic Case
  12. 12. The Strategic Case: Questions to Ask <ul><li>Are there institutional drivers for: </li></ul><ul><li>The implementation of an enterprise directory / identity management solution? </li></ul><ul><ul><li>Need to manage ‘non-standard’ users more efficiently, need to manage all users more efficiently! </li></ul></ul><ul><li>Single (simplified) sign-on / devolved authentication? </li></ul><ul><ul><li>System for both internal and external resources. </li></ul></ul><ul><li>Collaborative access to resources within other institutions? </li></ul><ul><ul><li>HE / FE collaboration; franchises in other countries. </li></ul></ul><ul><li>Research collaboration? Private sector collaboration? </li></ul><ul><ul><li>‘Virtual Organisation’ support; third-stream funding opportunities. </li></ul></ul>
  13. 13. Strategic Case: Example – Kings College London <ul><li>VISION STATEMENT: “Using a single password, postgraduate students can access not only King’s own electronic resources but also those of other universities and institutions by co-operative agreements. </li></ul><ul><li>VISION STATEMENT: “Provide services which reduce the burden of administration and information management.” </li></ul><ul><li>VISION STATEMENT: “Provide services which facilitate scholarly communication, collaboration and research </li></ul><ul><li>Federated access management allows not only single sign-on internally using an institutional password, but also allows users to access resources (such as VLEs) at other institutions using that same password (i.e. no need to register elsewhere). </li></ul><ul><li>Devolved authentication means that institution do not have to administer Athens accounts and single sign-on reduces the need for libraries to manage people as well as resources. </li></ul><ul><li>Federated access management supports the adoption of ‘virtual organisations and key research tools (such as open access repositories) have been ‘federated’. </li></ul>
  14. 14. Federated Access: Developing a Business Case The Options Appraisal
  15. 15. Institutional Options <ul><li>BECOME A FULL MEMBER OF THE FEDERATION USING COMMUNITY SUPPORTED TOOLS </li></ul><ul><ul><li>COSTS: Institutional effort to implement software, join federation and enhance institutional directories </li></ul></ul><ul><ul><li>BENEFITS: Full institutional control, skilled staff and access management solution for internal, external and collaborative resources </li></ul></ul><ul><li>BECOME A FULL MEMBER OF THE FEDERATION USING TOOLS WITH PAID-FOR SUPPORT </li></ul><ul><ul><li>COSTS: Cost of support from supplier and institutional effort in liaison with supplier and Federation </li></ul></ul><ul><ul><li>BENEFITS: Full support in implementation and access management solution for internal, external and collaborative resources </li></ul></ul><ul><li>SUBSCRIBE TO AN ‘OUTSOURCED IDENTITY PROVIDER’ TO WORK THROUGH THE FEDERATION ON YOUR BEHALF (SUCH AS USE OF CLASSIC ATHENS WITH THE GATEWAYS) </li></ul><ul><ul><li>COSTS: Subscription costs to external supplier (from July 2008) and internal administration role </li></ul></ul><ul><ul><li>BENEFITS: Minimum institutional effort to achieve access to external resources only </li></ul></ul>
  16. 16. JISC Options <ul><li>Options appraisal for Services taken at the point where technology, capability and requirements of the community had been fully established through JISC Development programmes. </li></ul><ul><li>Move Athens to subscription model, no future development . </li></ul><ul><li>Continue funding Athens, no future development . </li></ul><ul><li>Continue funding Athens, continue funding development . </li></ul><ul><li>Transition to federated service, no continued Athens funding . </li></ul><ul><li>Transition to federated service, limited Athens support . </li></ul><ul><li>Transition to federated service, continued Athens support . </li></ul>
  17. 17. Options Appraisal: JISC example Not recommended as a strategically sound direction for JISC. Recommendation <ul><li>Fails to meet JISC Strategy on several fronts – ceasing to be innovative and world class status; failing to be economic and efficient in terms of services offered. </li></ul><ul><li>Negative reaction from community. </li></ul><ul><li>Access Management a core function of service provision within the strategy. Failure to support will impact on all areas of JISC. </li></ul><ul><li>Lack of innovation affects UK / JISC International standing. </li></ul>Risks <ul><li>Release of JISC service funds. </li></ul><ul><li>Meets approach of the JISC Development – Service model in terms of moving robust services to subscription models. </li></ul>Benefits Eduserv have announced that they will charge a maximum of 50p per account per institution per annum for continued provision of the Athens service. At current service provision (3.5 million user accounts), the cost to UK Higher and Further Education Institutions will be £1,750,000. This represents an increase in cost of the community of £1,120,000 above the JISC managed solution currently supplied. Cost This option would amount to JISC taking the decision to cease financially supporting access management solutions for the community. It presumes that the Athens service is now a stable and self-sustaining model, and that an appropriate subscription model can be applied across HEIs, FEIs and Service Providers. Overview
  18. 18. Federated Access: Developing a Business Case The Financial Case
  19. 19. Financial Case: procurement and commercial issues <ul><li>JISC ‘Institutional Preparedness’ Study (170 institutions): </li></ul><ul><li>Directory Services: </li></ul><ul><ul><li>66% HE / 69% FE use Active Directory </li></ul></ul><ul><ul><li>31% HE / 13% FE use Novell eDirectory </li></ul></ul><ul><ul><li>27% HE / 31 % FE use OpenLDAP </li></ul></ul><ul><li>Outsourcing / Delegation of Identity Management: </li></ul><ul><ul><li>2% of HE / 0% FE outsource directory / identity management </li></ul></ul><ul><ul><li>25% HE allow departmental control of identity management </li></ul></ul><ul><li>Current use of Athens: </li></ul><ul><ul><li>Classic Athens: 57% HE / 78% FE </li></ul></ul><ul><ul><li>AthensDA: 35% HE / 7% FE </li></ul></ul>
  20. 20. Financial Case: implementation and ongoing <ul><li>Costs associated with adopting federated access management need to be assessed on an institution by institution basis. </li></ul><ul><li>Depend on starting point (state of directory services, choice of directory services, use of Athens, size of institution etc. etc.). </li></ul><ul><li>Depends on ‘end’ goal (full single sign-on implementation or more lightweight approach). </li></ul><ul><li>Use case studies of ‘early adopters’ to judge where you might be – please contact me. </li></ul><ul><li>Talk to the early adopters (they are very nice). </li></ul><ul><li>NMI-EDIT full Enterprise Directory project example: £250,000 capital, £130,000 recurrent. </li></ul><ul><li>Simple adoption of federated access management: £5,000. </li></ul><ul><li>Early adopter projects: £50,000. All successful within these constraints. </li></ul><ul><li>Athens: no more than 50p per user account for all Athens systems. </li></ul>
  21. 21. Federated Access: Developing a Business Case The Project Management Case
  22. 22. Technical Capability / Management Buy-In
  23. 23. Achievability: Skill Set (with thanks to Swish!) Setting up a CVS Repository; Populating (importing) new data;Check out/in. CVS Profiles, bindings and extensions SAML Format and content of XML files ; Namespace (xmlns) definition and use ; XML Schema definitions XML Log4j and log4cpp configuration options ; Analyzing stack traces and locating configuration errors. Java Configuration files: server.xml, workers2.properties, tomcat-users.xml Application WAR deployment ; Use of conf, webapps, WEB-INF and classes directories. Mod_jk use and Tomcat modification to use it ; “ant command” and editing build.properties and build.xml files.Build WAR and dist files. Tomcat Writing simple web pages ; Meaning of every HTTP code ; CSS authoring HTTP and HTML PKI ; Use of the openssl command and every option Trust stores and certificate stores Obtaining certificates, installing them, converting to/from different encoded methods. Building certificate chains. SSL Knowledge of the configuration files for the webserver and being able to correctly specify values for all directives. Virtual host configuration with SSL. Adding modules, building modules Configuring a content management system to host documentation about procedures and configuration file changes. Webserver (Apache, IIS) Security policy management for controlling port use . Where to install applications, configuration files. Syslogd operation, writing startup services, obtaining and inspecting packet dumps, writing scripts to monitor and control multiple log files in many windows and using filtering, sorting and pattern matching to reformat output. Operating System Minimum requirements Skill area
  24. 24. In Summary <ul><li>All institutions have options to consider regarding the adoption of federated access management. </li></ul><ul><ul><li>Gateways ensure that it is your decision and not ‘chicken and egg’. </li></ul></ul><ul><li>Institutions have a wide range of drivers that support the adoption of federated access management. </li></ul><ul><ul><li>Collaborative eLearning, eResearch, ePortfolios, Open Access Repositories, Information / Knowledge Strategies. </li></ul></ul><ul><li>It is important that this is planned and considered on an institutional basis. </li></ul><ul><ul><li>What is the best fit for your institution? </li></ul></ul><ul><ul><li>What’s in your strategy already? </li></ul></ul><ul><li>Lots of resources available to help in the planning process. </li></ul>
  25. 25. References and Contacts <ul><li>CONTACTS </li></ul><ul><li>Nicole Harris, JISC Programme Manager: [email_address] ; 07734 058308. </li></ul><ul><li>JISC Access Management Outreach Team: [email_address] </li></ul><ul><li>REFERENCES </li></ul><ul><li>JISC InfoNet: www.jiscinfonet.ac.uk </li></ul><ul><li>NMI-EDIT: www.nmi-edit.org </li></ul><ul><li>JISC Support: www.jisc.ac.uk/federation </li></ul><ul><li>UK Access Management Federation: www.ukfederation.org.uk </li></ul>

×