Main Nav

Thursday
Nov 8th, 2012
2:40 PM - 3:30 PM
Mile High Ballroom 4E/4F
Mountain Time

Although identity management is a relatively mature concept, its true value to institutions may still not be entirely understood. Hear about the benefits attained by three institutions that have taken very different approaches to identity management. Each institution also has important suggestions and key lessons learned for success.

Speakers
Resources

Comments

IdM2: Plan before buying a IdM product. #edu12 #E12_SESS122

IdM2: Products will require consulting services. Make sure that is part of the budget process. #edu12 #E12_SESS122

IdM2: IdM is not an IT project, it's a campus project. You need buy-in and participation across campus. #edu12 #E12_SESS122

IdM3 (Princeton): Used PeopleSoft IdM package. #edu12 #E12_SESS122

IdM3:Prior to full IdM... "I see dead people" #edu12 #E12_SESS122

IdM3: Data Governance already existed from PeopleSoft group. Leveraged for IdM as well. #EDU12 #E12_SESS122

Idm3: Established a "Person Office" within IT. Used for person & ID related policies. #Edu12 #E12_SESS122

IdM2: George Washington EDU #edu12 #E12_SESS122

IdM1: Mass College for Art & Design. #edu12 #E12_SESS122

IdM3: Policy changes implemented via config changes not new coding. #edu12 #E12_SESS122

IdM3: Implementation of IdM product is just as huge as a ERP system including involving campus stakeholders. #edu12 #E12_SESS122

IdM3: When using consultant/vendor, make sure they know HigherEd environment and politics. #edu12 #E12_SESS122

W/ faculty: create accounts w/ exp. date of 180 days. Get active faculty via ERP each sem & extend 180 days. #E12_SESS122 #edu12

When going for IdM: Sell to C-Suite first with goals they will understand, then work your way down. #edu12 #E12_SESS122

Defining the person is the first step in IdM. #edu12 #E12_SESS122


Comments

IdM2: Plan before buying a IdM product. #edu12 #E12_SESS122

IdM2: Products will require consulting services. Make sure that is part of the budget process. #edu12 #E12_SESS122

IdM2: IdM is not an IT project, it's a campus project. You need buy-in and participation across campus. #edu12 #E12_SESS122

IdM3 (Princeton): Used PeopleSoft IdM package. #edu12 #E12_SESS122

IdM3:Prior to full IdM... "I see dead people" #edu12 #E12_SESS122

IdM3: Data Governance already existed from PeopleSoft group. Leveraged for IdM as well. #EDU12 #E12_SESS122

Idm3: Established a "Person Office" within IT. Used for person & ID related policies. #Edu12 #E12_SESS122

IdM2: George Washington EDU #edu12 #E12_SESS122

IdM1: Mass College for Art & Design. #edu12 #E12_SESS122

IdM3: Policy changes implemented via config changes not new coding. #edu12 #E12_SESS122

IdM3: Implementation of IdM product is just as huge as a ERP system including involving campus stakeholders. #edu12 #E12_SESS122

IdM3: When using consultant/vendor, make sure they know HigherEd environment and politics. #edu12 #E12_SESS122

W/ faculty: create accounts w/ exp. date of 180 days. Get active faculty via ERP each sem & extend 180 days. #E12_SESS122 #edu12

When going for IdM: Sell to C-Suite first with goals they will understand, then work your way down. #edu12 #E12_SESS122

Defining the person is the first step in IdM. #edu12 #E12_SESS122