Provisioning People and Applications

Frank Grewe

Office of Information Technology

University of Minnesota

fjg@umn.edu

o=University of Minnesota,c=US

Enterprise directory services which provisions applications and people, who…

Live, work, play, in:

• umn.edu (Minneapolis & St. Paul)• d.umn.edu (Duluth)• mrs.umn.edu (Morris)• crk.umn.edu or UMCrookston.edu (Crookston)• med.umn.edu or fairview.org or mayo.org (Medical

School)• ext.umn.edu or co.county.mn.us (Extension Services)• Etc., …

Primary Data Sources

HR

Guest

Sponsored

DeptAccts

WebCT

StudentOrgs

CSOM

AlumniAssoc

Registrar

Object

Supplemental Data Sources

Depts

AcctMgmt

FoodServices

Housing

UCard

STARS

Attributes

Identifiers

• umnDID

• InternetID

• EmplID

• PatronID

• UCardID

• DonorID

• WhocaresID

Identifier Mapping

• Directory provides seamless movement between applications which require different identifiers.

• Choice of identifier by an application is most often intuitive.

• Applications developers can make bad choices.

Applications

• Databases– Library Patron Database– Sports and Rec– Food Services (Dorms)

Applications

• UNIX– Coordinate Campuses– IT Labs

• Network OS– NT4– NT5 (aka AD)– Novell

Applications

• WebCT– Data flow in both directions

• Public Portals– Guest account mechanism– Applications can populate attributes– One ID across all portals– Identifier mapping allows transition to full

account status.