FSU Metadirectory Project The Issue of Identity Management Executive Overview

The Problems 1.Individuals have to remember too many different names and passwords to access our systems 2.We have too many electronic directories 3.Many of our systems (electronic and in- person) still rely on asking an individual for their Social Security Number as a method for authentication

The SSN Problem SSN is used as a method for authenticating students and employees via web and in-person challenges Mandates to protect SSN abound SSN is still required for certain business processes (HR, external identity of students, etc.)

The SSN Problem Some progress towards downplaying SSN use has been implemented: –Modify certain systems to use phrases like “student number” or “employee ID” –SSNs have been removed when not absolutely necessary for various reports –PeopleSoft only uses SSNs as required for business purposes and not as an identity challenge

The Proposal This proposal is an attempt to define identity terms and solve the SSN/multiple identity problem Proposal: –FSUID = new public “login name”/password –FSUSN = new “SSN-like” private number –Metadirectory will manage this information

The Identity Problem C.A.R.S. (”ldap1”) –All students, faculty & staff plus visitors –Tied into automated systems on campus, such as FSUCard, HRMS, etc. –Used for authorizing “garnet/mailer” servers, dialup service

The Identity Problem C.A.R.S. (”ldap1”) –Blackboard authentication

The Identity Problem O.P.S. (Secure Login; ”ldap2”) –All students, faculty & staff plus visitors –Tied into automated systems on campus, such as FSUCard, HRMS, etc. –Used for authorizing many administrative applications (many, but not all of which, will be initially replaced by PeopleSoft functionality)

The Identity Problem Web registration for classes (SSN)

The Identity Problem Administrative –Managed in the enterprise “FSU” Microsoft Active Directory (Outlook users) –Semi-manual account management –Mostly used by some ~6,000 administrative employees

The Identity Problem Netware Account –Provides file service –Managed by User Services in OTI –Manual account management –Mostly used by some ~6,000 administrative employees

The Identity Problem PeopleSoft Account(s) –Many instances exist –Driving the need for a common directory

The Identity Management Solution The metadirectory provides us with the technology and flexibility to merge our different electronic identities We will convert to using one FSU Identity; one “FSUID”, with one password (this is known in the business as “Single Signon”) Our users will be able to log into our current systems and especially the new PeopleSoft instances using one common name and password

The FSU Metadirectory

Metadirectory and SSN The metadirectory also provides a great framework for migrating away from using SSN as a “private authentication number” We will generate a new private number (call it your “FSUSN”), that can be used to authenticate people

Metadirectory Project Resources Integrated with ERP project planning Required technology infrastructure is integrated with ERP and OTI infrastructures Security and reliability are utmost concerns Joint effort with OTI (ACNS, AIS, US, IRM), ERP, Registrar/Admissions and ODDL personnel actively participating

Metadirectory Project Timeframe Scheduled to have LDAP1/LDAP2/AD/PS Metadirectory in production by mid-March and available for PeopleSoft authentication Deepter PS integration by HR “go-live” Full CARS/Secure Login/Active Directory/Novell integration by July of 2005 Complete conversion from SSN to FSUSN by January of 2006 Track project at