Implementing
                                    Confluence at Harvard"Enabling enterprise collaboration for "..about 8,000...
Agenda"  •    Current state"  •    Context"  •    Requirements"  •    Integration"  •    Questions"
Context      "
Context      "
iCommons"•  iSites – "  •  Home-grown LMS "  •  Tool-based approach +"  •  Existing all-in-one wiki/blog/     discussion t...
Requirements and Goals"
Requirements - basic"   •  Security"   •  User privacy"   •  Easy access for external collaborators"   •  Simple, real-tim...
Requirements - extra"•  iSites integration"•  Terms-of use acceptance agreement"•  One-step addition and permissioning of ...
Why Confluence?"•  Evolving iSites tool concept" •  build/maintain/enhance à integration of proven open source and    comm...
Implementation Options"
Users and Groups"GOAL – "Don’t reinvent the wheel -- let Confluence be Confluence"
LDAP" ""Aargh.. (for us, anyway)"
Virtual Directory" Aargh, again.."                   Virtual Directory	     LDAP	                                         ...
Solution: Simplify"•  Map users in our own table"•  At the iSites end, create a REST group service"•  At the Confluence end...
Solution"                                   Confluence	                     "" SSO	                                        ...
Provisioning from iSites" "
Recent Updates in iSites" "
Terms of Use" "
Conclusion"Simple is best"Let Confluence be Confluence"
Integration strategy? Do what you must, but, to theextent possible, just step aside and let #Confluence doits thing.     #...
Thank you!
Implementing Confluence at Harvard
Implementing Confluence at Harvard
Implementing Confluence at Harvard
Implementing Confluence at Harvard
Implementing Confluence at Harvard
Upcoming SlideShare
Loading in...5
×

Implementing Confluence at Harvard

890

Published on

Implementing Confluence as an enterprise service in a highly decentralized university setting presents a number of technical and organizational challenges. We'll touch on the customizations we've made to integrate Confluence with both the Harvard infrastructure in general and with our course management system, iSites, in particular. We'll discuss our technical requirements going in and our experience meeting those requirements by implementing SSO, group management, auto provisioning and categorization, and FERPA compliance by means of custom plugins and other techniques that we believe will continue to be sustainable as we move forward. We'll also discuss organizational requirements around support and provisioning and our experience with the support model we're using. Finally, we'll discuss the ways in which Confluence is being used across the university, for both academic and administrative purposes.

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

  • Be the first to like this

No Downloads
Views
Total Views
890
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Implementing Confluence at Harvard

  1. 1. Implementing
 Confluence at Harvard"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, apolice department, 600 buildings, and an arboretum"Carter Snowden!iCommons Group"Harvard University Information and Technology"carter.snowden@harvard.edu"
  2. 2. Agenda" •  Current state" •  Context" •  Requirements" •  Integration" •  Questions"
  3. 3. Context "
  4. 4. Context "
  5. 5. iCommons"•  iSites – " •  Home-grown LMS " •  Tool-based approach +" •  Existing all-in-one wiki/blog/ discussion tool - "" •  Distributed support model – school-level liaisons +"
  6. 6. Requirements and Goals"
  7. 7. Requirements - basic" •  Security" •  User privacy" •  Easy access for external collaborators" •  Simple, real-time permissioning" •  Support and provisioning" "
  8. 8. Requirements - extra"•  iSites integration"•  Terms-of use acceptance agreement"•  One-step addition and permissioning of users and groups for Confluence space admins"
  9. 9. 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"
  10. 10. Implementation Options"
  11. 11. Users and Groups"GOAL – "Don’t reinvent the wheel -- let Confluence be Confluence"
  12. 12. LDAP" ""Aargh.. (for us, anyway)"
  13. 13. Virtual Directory" Aargh, again.." Virtual Directory LDAP iSites Group DB
  14. 14. 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" ""
  15. 15. Solution" Confluence "" SSO Via Space Permissions page Unique id (private) Utility plugin Authenticator plugin Can view/administer Check Privacy settings; Member-of Get safe id Get updated name and email if changed Group service iSites Group Service LDAP Mapping table
  16. 16. Provisioning from iSites" "
  17. 17. Recent Updates in iSites" "
  18. 18. Terms of Use" "
  19. 19. Conclusion"Simple is best"Let Confluence be Confluence"
  20. 20. Integration strategy? Do what you must, but, to theextent possible, just step aside and let #Confluence doits thing. #summit12
  21. 21. Thank you!
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×