A New Face for Identity Management: Architecting an Improved Solution for Identity Management at FSU

    Session Number: 31563
    Track: Security and Audit
    Sub-Categorization: Identity Mgmt
    Session Type: Case Study
    Tags: Campus Community, ID management, LDAP
    Primary Presenter: Diane Higgins [Network Specialist - Florida State University]
    Co-Presenter: Kevin Gele [Specialist Master - Deloitte]
    Time: Mar 19, 2013 (04:15 PM - 05:15 PM)
    Room: 141

    Learning Objectives from Session: 1. Understand the challenges of converting from a mixture of programming languages and database type to CWS and SOA
    2. Understand the different provisioning needs for onboarding applicants, admitted applicants, specialty students, employees and visitors.
    3. Understand the challenges created by keeping legacy systems in sync with Campus Solutions during the two year implementation of all of the Campus Solutions modules. The plan must also take into consideration the implementation of Oracle Identity Manager which will begin implementation after Campus Solutions is fully live.

    Product: PeopleSoft
    Version Presenting: PS 9.0
    Level of Customization: Customization
    Level of Partner Integration: Select a Value
    Project Phase: Implementation
    Project Go Live: Q4 2012
    Target Audience: Functional
    Audience Level: Intermediate
    Your Training in this Area: Diane has a degree in Management Information Systems and has attended various training sessions on Master Data Management and Identity Management in general.

    Description:  Florida State University uses a universal identifier known as the FSUID for logging into the student legacy systems and PeopleSoft HCM. It is a combination of PERL and Java utilizing mainframe, DB2 and Oracle databases. With the implementation of Campus Solutions which will become the master data management hub for student, employee and visitor data at FSU it was necesssary to reconfigure this process. The new process must register constituents into Campus Solutions and message bio-demo data to HCM. It must also keep the legacy tables in sync throughout the two year implementation of all the Campus Solutions modules. The new process will utilize Constituent Web Services and SOA to provision accounts for Campus Solutions, LDAP, Active Directory, Blackboard and Exchange.