1 / 12

The Changing Role of the Technologist as Higher Ed Embraces the Cloud

The Changing Role of the Technologist as Higher Ed Embraces the Cloud. Michele Decker, University of Notre Dame Jacob Farmer, Indiana University Derek D Owens, University of Notre Dame Kris Steinhoff, University of Michigan. Relationships.

nevan
Download Presentation

The Changing Role of the Technologist as Higher Ed Embraces the Cloud

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Changing Role of the Technologist as Higher Ed Embraces the Cloud Michele Decker, University of Notre Dame Jacob Farmer, Indiana University Derek D Owens, University of Notre Dame Kris Steinhoff, University of Michigan

  2. Relationships The success of a cloud deployment is dependent on an effective and diverse team. The engagement pattern for the team is very different than for on-premise software. If you don't include a lawyer, you may be doing it wrong.

  3. Systems Integration • Scripting and using vendor APIs • Creating ad hoc tools • Integrating with campus systems • Filling gaps • Working with vendors • Identifying bugs • Defining feature requests • Broad knowledge • Communicating requirements and changes

  4. Federated Identity Having flexible IAM practices and a federation infrastructure in place, can greatly reduce the complexity of integration.

  5. Federated Identity • Benefits for Vendor/SP • Don’t have to maintain user accounts • Common way to integrate with enterprise customers (reduces startup time) • NET+ involvement opens a large market • Risks/Costs for Vendor/SP • Install and maintain SP software • Box still isn’t an InCommon SP, have to manually update metadata • Change their login flow • Custom branding for enterprises

  6. Federated Identity Benefits for Institution/IdP • Don’t have to maintain/sync user passwords to third party • Common integration method • Auto-provisioning • Internet2 network

  7. Federated Identity Risks/Costs for Institution/IdP • Not all of features/service offerings from Vendor/SP are integrated with SSO • Can’t restrict/control all login flows • email invitations to sign-up • Vendor/SP not able to accommodate multiple IdPs for one enterprise • Auto-provisioning (lack of control of the process)

  8. Federated Identity Skills needed to operate a Shibboleth IdP • Technical Skills https://wiki.shibboleth.net/confluence/display/SHIB2/IdPSkills • Policy Understanding

  9. Security, Trust, Assurance • Sensitive Data • HIPAA, FERPA • Audit, Compliance, IT Governance • SAS70 II • Logging • Monitoring • “Low-Touch”, trust of vendor • Trust but verify • Credentials • Non-Federated access, alternate credentials • Exit Strategy

  10. Evolving Skills • Good communication, facilitation, and “whiteboarding” skills • Oral and written communication skills are fundamental to success • Persistence and ability to live with chaos • Cloud computing is fast-changingNew delivery methods appear frequently • Requirements and processes change frequently • Breadth of knowledge • Jack Of All Trades, Polymath, "Renaissance Man" • Focus upon integration, less so on building • "Infrastructure Enablers"

  11. Evolving Skills • Can’t control progress of vendor • “Keeping up with the KardashiansJoneses” • Let them “do their thing”Don’t have to understand all the nuts and bolts • Continuous review/revision of service and integration

  12. Questions?

More Related