You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 52 Next »

Face 2 Face Planning

Face2Face 2009 Survey

Next Face 2 Face

Logistics:

Location: Arlington, VA at the Crystal Gateway Marriott.
Dates: Wednesday, April 29th and Thursday, April 30th.
Venue: Crystal Gateway Marriot. See the Internet2 Hotel Site for more information about the room block and registration details.
Registration Site: http://events.internet2.edu/2009/spring-mm/registrationintro.html
Registration opens the first week of February, 2009. There will be a registration fee ($235) for this meeting. See the registration site for details.

Agenda for the Next Face2Face meeting.

Wednesday - April 29th

  • Session Chair Gathering - final planning
  • 5PM to 8PM - Social Reception

Thursday - April 30th

  • 8AM to 5PM

Morning Presentations:

  • Enterprise Authorization - Marina Arseniev, Chair
    • Enterprise Authorization presents challenges from the technology perspective but surfaces even more challenges from the business and cultural requirements perspective. The recent decision to put Internet2's SIGNET technology on hold is one indicator of the difficulty of erecting an institution-wide authorization solution. But what is meant by the "Enterprise"? What scope is assumed? What is the appropriate level of granularity? For a truly effective strategy that meets accountability and audit demands, must authorization encompass Student Services, Research Management, Payroll / HR Services, Athletics, Financial Systems, and other business and academic units of an institution? And what about integration with vendor packages or popular new community source solutions such as Kuali? Do authorization and access control primarily encompass web services or must they include operating system access, log file access, door keys, and password access? Not only is it enough to know who had access to what and when, it is also important to know who granted access to whom and when, and who revoked access and when.
    • This session will discuss why enterprise authorization is so elusive for so many of our institutions; it will be a forum to share successes and failures. The goal is to define what specific actionable steps or decisions architects across our campuses might be able to make that bring vision and clarity back to their organizations.
  • Kuali on Campus - David Walker, Chair
    • Over the past few years, the Kuali Foundation has become a major force in the creation of community source administrative software for use in higher education. Work is in progress on a growing list of applications, including Kuali Financial System, Kuali Student, and Kuali Coeus (research administration). These applications are being designed to utilize a common middleware layer, Kuali Rice, which provides a service bus, workflow, access to identity management, notification, and presentation services.
    • This session will provide a brief introduction to Kuali, followed with presentations by the panel members about their plans for use of Kuali applications and middleware.
      • University of California: Assessment of Kuali Rice for Single and Multiple Campus Applications
      • (2-3 more participants, depending on time)
  • SOA and Interoperability - Tom Dopirak, Chair
    • This session will focus on the issues of utilizing SOA across organizational boundaries but within a federation. Underlying SOA technology typically consists of a web services framework supported by service registries, enterprise service buses , identity management and access management systems. What kinds of policy agreements and what kinds of technical agreements are necessary for federated SOA to be possible? What additional agreements are necessary for existing federations to support SOA interoperability? What services are likely to be shared in a federation using SOA architectural ideas and supporting technology?
  • Federation support in Kuali and other SOA/ROA systems - R.L. "Bob" Morgan, Chair
    • Federated access to web-based applications by users using web browsers is becoming mainstream in higher ed. Meanwhile, campuses are developing web services frameworks to support service-oriented application integration on their campuses. The lack of widely-accepted standards for web service authentication leads to the likelihood that each campus does its own thing regarding client process authentication to web services. This may preclude the possibility of inter-campus web service access. The same skew may apply across different application environments.
    • Are there compelling use cases for inter-campus process-to-service access? Does common deployment of SOA-based applications like Kuali Student create more of these? Are there standards that we can promote to make such access likely? Can we leverage trust federations set up for browser-based access?
    • We will consider all these questions and find answers or at least increase the likelihood of answers being found later.

Afternoon Working Groups:

TBD

Report Out from Working Groups

Past Face 2 Face Meetings:

Past Face2Face Meetings

  • No labels