Single SignOn

1
Single Sign-On

• Mike Conlon
• Office of Information Technology

2
Desired State

• One person, one identity
• Identity management across UF systems desktop,
  web-based, enterprise
• Support multiple modalities for directory
  services LAN-based, web-based, enterprise
• Provide public and private identifiers
• Authoritative source for identity and directory
  information
• Move toward single sign-on

3
Current State

• Four production directory systems LDAP, UF
  Registry, Kerberos, Netware Directory Services
  (NDS)
• Two directory systems to be added Active
  Directory (AD), PeopleSoft
• Existing integration between LDAP and UF Registry
• Adhoc integration with Kerberos and NDS
• UF Registry provides authoritative source
• GatorLink (public), UFID (transactional), UUID
  (private) provide identifiers

4
Why Six Systems?

• LDAP is the open standard for web-based
  applications.
• Active Directory is the standard for desktop
  users
• NDS is the legacy system for desktop users
• PeopleSoft is the future enterprise system
  PeopleSoft will use LDAP directly in future
• Kerberos is the open standard for authentication
• UF Registry is the current authoritative source
  with a known data model and service provider for
  legacy systems

5
Roadmap

• Implement AD based on Kerberos identity provide
  a foundation for future desktop integration.
  Spring 2003 through 2005
• Use LDAP and Kerberos to authenticate PeopleSoft
  (in place today)
• Provide standards-based authentication mechanism
  for free-standing web apps (in place today)
• Consider the future of NDS
• Integrate UF Registry and PeopleSoft (work in
  progress)
• 2004 Integrated enterprise directory systems
  AD, LDAP, PeopleSoft, Kerberos, Registry, NDS