1 / 7

Some Thoughts on IdM Steve Devoti devoti@wisc

Some Thoughts on IdM Steve Devoti devoti@wisc.edu. UW-Madison. Long Ago. The need for centralized directory services was recognized Central IT driven Support for authentication and course grained authorization. University Directory Services. Moving Along.

oki
Download Presentation

Some Thoughts on IdM Steve Devoti devoti@wisc

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Some Thoughts on IdMSteve Devotidevoti@wisc.edu

  2. UW-Madison

  3. Long Ago • The need for centralized directory services was recognized • Central IT driven • Support for authentication and course grained authorization

  4. University Directory Services

  5. 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

  6. 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

  7. 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

More Related