How 11 US universities are
    using Gluu EDU to
  normalize and support
     a Shibboleth IdP
        November 16, 2012
Today's Agenda                    Hosted by:

1. Introduction & Overview

2. Typical Gluu Deployments

3. The Business Case for a
managed IdP Service           Michael Schwartz
                              Gluu CEO and Founder

4. Gluu Demo

5. Q&A
Gluu Server: Overview
Typical Deployments:
Number of Servers

Scenario 1:
1 Production Server.


Scenario 2 (Most Popular):
1 Production Server, 1 Development Server.


Scenario 3:
2 Production Servers, 2 Development Servers
Typical Deployments:
Public vs. Private

Public:
Your server hosted on a dedicated Rackspace VM.
You maintain root access for SSH.



Private (Most Popular):
Your server hosted inside your firewall, on your own VM.
The Business Case: Buy vs. Build..?


With typical non-clustered Gluu EDU deployment:

1 Prod Server / 1 Dev Server = $2,400/yr
~ 3% FTE allocation

   For 3% FTE resource:
   ○   A GUI for Shibboleth (No More Manual XML!!)
   ○   Expert support from team of federation specialists
   ○   24/7 Monitoring
   ○   Config management
   ○   Revision Control
   ○   SLA reporting
SLA Reporting...
Gluu EDU Optionals:

● Integrated Multi-Factor Authentication

● Support for Radius

● OpenID Connect

● High Availability Clustered Deployment (Minimum 4 Servers)
DEMO
 - Identity Management
    ○   Attributes
    ○   LDAP Mapping
 - Certificate Management
 - Look and Feel
 - SAML
    ○   Trust Relationships
    ○   Federation Hosting
 - OpenID Connect
    ○   Two Factor Authentication
    ○   Scopes
    ○   Clients
    ○   Discovery
Q&A
                              Learn More at
                           http://gluu.org/edu



                                          We Support:
Some Gluu EDU Customers:


●   University of Kentucky
●   Oklahoma State University
●   The University of Oklahoma
●   Georgia State University
●   Franklin and Marshall

Gluu EDU Webinar: Shibboleth/SAML SSO

  • 1.
    How 11 USuniversities are using Gluu EDU to normalize and support a Shibboleth IdP November 16, 2012
  • 2.
    Today's Agenda Hosted by: 1. Introduction & Overview 2. Typical Gluu Deployments 3. The Business Case for a managed IdP Service Michael Schwartz Gluu CEO and Founder 4. Gluu Demo 5. Q&A
  • 3.
  • 4.
    Typical Deployments: Number ofServers Scenario 1: 1 Production Server. Scenario 2 (Most Popular): 1 Production Server, 1 Development Server. Scenario 3: 2 Production Servers, 2 Development Servers
  • 5.
    Typical Deployments: Public vs.Private Public: Your server hosted on a dedicated Rackspace VM. You maintain root access for SSH. Private (Most Popular): Your server hosted inside your firewall, on your own VM.
  • 6.
    The Business Case:Buy vs. Build..? With typical non-clustered Gluu EDU deployment: 1 Prod Server / 1 Dev Server = $2,400/yr ~ 3% FTE allocation For 3% FTE resource: ○ A GUI for Shibboleth (No More Manual XML!!) ○ Expert support from team of federation specialists ○ 24/7 Monitoring ○ Config management ○ Revision Control ○ SLA reporting
  • 7.
  • 8.
    Gluu EDU Optionals: ●Integrated Multi-Factor Authentication ● Support for Radius ● OpenID Connect ● High Availability Clustered Deployment (Minimum 4 Servers)
  • 9.
    DEMO - IdentityManagement ○ Attributes ○ LDAP Mapping - Certificate Management - Look and Feel - SAML ○ Trust Relationships ○ Federation Hosting - OpenID Connect ○ Two Factor Authentication ○ Scopes ○ Clients ○ Discovery
  • 10.
    Q&A Learn More at http://gluu.org/edu We Support: Some Gluu EDU Customers: ● University of Kentucky ● Oklahoma State University ● The University of Oklahoma ● Georgia State University ● Franklin and Marshall