Transcript
Page 1: Implementing Confluence at Harvard
Page 2: Implementing Confluence at Harvard

Implementing

Confluence at Harvard"

Carter Snowden!

Enabling enterprise collaboration for "..about 8,000 courses, 15 schools, 98 libraries, 21,000 students, 12,000 faculty, 98 libraries, who knows how many labs, 11 museums, a police department, 600 buildings, and an arboretum"

iCommons Group"Harvard University Information and Technology"[email protected]"

Page 3: Implementing Confluence at Harvard

Agenda"•  Current state"•  Context"•  Requirements"•  Integration"•  Questions"

Page 4: Implementing Confluence at Harvard

Context"

Page 5: Implementing Confluence at Harvard
Page 6: Implementing Confluence at Harvard
Page 7: Implementing Confluence at Harvard
Page 8: Implementing Confluence at Harvard

Context"

Page 9: Implementing Confluence at Harvard

iCommons"•  iSites – "•  Home-grown LMS "

•  Tool-based approach +"

•  Existing all-in-one wiki/blog/discussion tool - ""

•  Distributed support model – school-level liaisons +"

Page 10: Implementing Confluence at Harvard

Requirements and Goals"

Page 11: Implementing Confluence at Harvard

Requirements - basic"•  Security"•  User privacy"•  Easy access for external collaborators"•  Simple, real-time permissioning"•  Support and provisioning""

Page 12: Implementing Confluence at Harvard

Requirements - extra"•  iSites integration"

•  Terms-of use acceptance agreement"

•  One-step addition and permissioning of users and groups for Confluence space admins"

Page 13: Implementing Confluence at Harvard

Why Confluence?"•  Evolving iSites tool concept"

•  build/maintain/enhance à integration of proven open source and commercial products"•  Tight integration à loose(r) integration"

•  Confluence.."•  Is proven to integrate well with different SSO solutions"

•  Has a rich permissioning scheme"

•  Plugin architecture, templating, source availability provide flexibility"

Page 14: Implementing Confluence at Harvard

Implementation Options"

Page 15: Implementing Confluence at Harvard

Users and Groups"GOAL – "Don’t reinvent the wheel -- let Confluence be Confluence"

Page 16: Implementing Confluence at Harvard

LDAP"""Aargh.. (for us, anyway)"

Page 17: Implementing Confluence at Harvard

Virtual Directory"Aargh, again.."

LDAP

iSites Group DB

Virtual Directory

Page 18: Implementing Confluence at Harvard

Solution: Simplify"

•  Map users in our own table"•  At the iSites end, create a REST group service"•  At the Confluence end, create the necessary utilities to

consume the service"•  Use native Confluence user and group stores"

""

Page 19: Implementing Confluence at Harvard

""

LDAP iSites Group Service Mapping table

Authenticator plugin

SSO

Utility plugin

Group service

Unique id (private)

Check Privacy settings; Get updated name and email if changed

Get safe id Member-of

Can view/administer

Via Space Permissions page

Confluence Solution"

Page 20: Implementing Confluence at Harvard
Page 21: Implementing Confluence at Harvard

"Provisioning from iSites"

Page 22: Implementing Confluence at Harvard

"Recent Updates in iSites"

Page 23: Implementing Confluence at Harvard

"Terms of Use"

Page 24: Implementing Confluence at Harvard

Conclusion"Simple is best"Let Confluence be Confluence"

Page 25: Implementing Confluence at Harvard

#summit12

Integration strategy? Do what you must, but, to the

extent possible, just step aside and let #Confluence do

its thing.

Page 26: Implementing Confluence at Harvard

Thank you!


Top Related