70 likes | 185 Vues
This piece explores the evolution of centralized identity management systems (IdM) at UW-Madison, emphasizing the necessity for robust policy foundations and stakeholder involvement to ensure successful implementation. It discusses key elements such as web single sign-on (SSO), delegated administration, and group management, while also highlighting the significance of governance through leadership bodies like the Identity Management Leadership Group (IMLG) and the Authentication/Authorization Coordinating Team (ACT). Understanding the interplay between business needs and technology is critical for creating an effective roadmap for identity management.
E N D
Long Ago • The need for centralized directory services was recognized • Central IT driven • Support for authentication and course grained authorization
Moving Along • Web Initial Sign-on (I.e. web sso) • Delegated administration • Group Management • PKI • Provisioning • Problem: Lack of persistent structures to involve stakeholders • Prioritization • Governance
Step Back • Identity Management Leadership Group (IMLG) • High level • Make policy, provide executive support and resources • Authentication/Authorization Coordinating Team (ACT) • Director/manager level • Prioritization • Understanding of business and technology issues
Roadmap • What does this have to do with a roadmap? • A number of missteps when priorities were driven by central IT • Campus now owns the roadmap • Fills the policy gap. IdM/IAM can’t be successful without a policy foundation