the uw-madison iam experience
Post on 16-Apr-2017
485 Views
Preview:
TRANSCRIPT
The UW-Madison IAM Experience
Building our Dream HomePresented by Steve Devoti, Senior IT Architect© 2007 Board of Regents of the University of Wisconsin System
The UW-Madison needs to remodel and expand its IAM services
© 2007 Board of Regents of the University of Wisconsin System
You probably look a lot like us
© 2007 Board of Regents of the University of Wisconsin System
We are clearly not meeting the needs of campus, we lack a blueprint
© 2007 Board of Regents of the University of Wisconsin System
Analysis and an organized approach can get this thing built
© 2007 Board of Regents of the University of Wisconsin System
Form a project, assign resources and recommend a direction
© 2007 Board of Regents of the University of Wisconsin System
We had been working on a small space for over 4 years
© 2007 Board of Regents of the University of Wisconsin System
We decided to build it our selves
© 2007 Board of Regents of the University of Wisconsin System
There were no vendors that could meet our needs
© 2007 Board of Regents of the University of Wisconsin System
We love to build things
© 2007 Board of Regents of the University of Wisconsin System
Who knows? All the original decision-makers are gone!
© 2007 Board of Regents of the University of Wisconsin System
Overly complex design
© 2007 Board of Regents of the University of Wisconsin System
Never really structured as a project
© 2007 Board of Regents of the University of Wisconsin System
Customers are getting grumpy
© 2007 Board of Regents of the University of Wisconsin System
For 4 years, customers have been told that PASE will solve everything
© 2007 Board of Regents of the University of Wisconsin System
The executive sponsor decided it was time for some changes
© 2007 Board of Regents of the University of Wisconsin System
A new enterprise architect was assigned
© 2007 Board of Regents of the University of Wisconsin System
A “real” project manager was assigned
© 2007 Board of Regents of the University of Wisconsin System
The team reexamined the requirements and the decision to build
VS
© 2007 Board of Regents of the University of Wisconsin System
We formalized our requirements and did a high level evaluation of the options
Functional/Non Functional
IAM Category Scope Requirement Compliance
Module or Feature
Effort
F Authorize System
Shall provide the ability to define combinations of create, retrieve (read), update (modify) and delete permissions to created appropriate system roles (e.g. "Affiliation Manager")
None Authorization Manager Difficult
F Authorize SystemThe system shall support integration with the institutional and/or standards-based authentication mechanisms (e.g. pubcookie, Shibboleth, SAML).
None Authentication Manager Moderate
F Authorize SystemThe system shall support an "auditor" role which allows a subject to read and create reports from system logs, but allows no other system access.
None Authorization Manager/UI Moderate
F Log System Shall support logging of, and reporting on governance activities. Partial Log/Audit
facility Easy
See: WIBuyVSBuild.xls
Build vs. Open Source vs. Buy
© 2007 Board of Regents of the University of Wisconsin System
We also completed a high-level pros and cons analysis
• Acquire Total Solution (Commercial Vendor) Pros:– Consulting resources. Consulting resources are readily available to assist in
commercial vendor implementations.– Provisioning. Commercial vendor identity management suites include advanced
provisioning functionality.– Workflow. Commercial vendor identity management suites include workflow.– Functionality. In addition to provisioning, many vendor suites include other
advanced identity management functionality that might be useful to the organization (web access control, federation services, virtual directory or meta-directory, etc.).
• Acquire Total Solution (Commercial Vendor) Cons:– Cost. Is more expensive than some other solutions.– Lack of higher education community. Though there is high adoption of
commercial identity management software in private industry, there is much less adoption in higher education, particularly at large institutions
See: WIProsAndCons.xls
© 2007 Board of Regents of the University of Wisconsin System
We decided that the Grouper/Signet solution best met our needs
© 2007 Board of Regents of the University of Wisconsin System
We went to some camps, and installed a POC system
© 2007 Board of Regents of the University of Wisconsin System
The natives were getting even more restless
© 2007 Board of Regents of the University of Wisconsin System
Priorities have changed
© 2007 Board of Regents of the University of Wisconsin System
Our customers wanted us to address provisioning first
© 2007 Board of Regents of the University of Wisconsin System
That was going to take a lot of building or maybe purchase of another product
© 2007 Board of Regents of the University of Wisconsin System
The only reasonable thing to do was look at vender solutions
© 2007 Board of Regents of the University of Wisconsin System
We did proof-of-concepts with Oracle and Sun
© 2007 Board of Regents of the University of Wisconsin System
Our sponsor was exploring ways to pay for the solution
© 2007 Board of Regents of the University of Wisconsin System
Through hard work and masterful persuasion funding was secured
© 2007 Board of Regents of the University of Wisconsin System
We began an RFP, dividing the work into 3 high-level capabilities
Directory Services
IdentityManagement
Integration
Access Management
History
Support
Cost
© 2007 Board of Regents of the University of Wisconsin System
Each capability section was built with standard bricks
See: WIRFPSpecs.doc
© 2007 Board of Regents of the University of Wisconsin System
Capabilities, functions and “other considerations” were weighted
© 2007 Board of Regents of the University of Wisconsin System
We ended up with something like this:
3 Web Access Management Capability Rating Guidance Points Total Points= 3,400
We define Web Access Management Capability as a central policy and enforcement infrastructure capable of protecting heterogeneous web resources for the purpose of providing users with single sign-on. Note, in the context of this RFP, Web Access Management includes federation functionality and the protection of SOAP-based web services.
3.1.
Architecture: Describe at a high level the elements and technologies that make up this capability and their relation to each other. Provide diagrams. What are the advantages of this architecture? Specify any disadvantages or limitations of this architecture. If your solution supports multiple high-level configurations, describe the advantages and disadvantages of each. Describe the logical architecture of the servers that make up your solution.
SHOULD follow good application architecture practices with an architecture that is compatible with the University of Wisconsin's Common Systems technology infrastructure.
544
3.1.1.Policy Administration Points (PAPs): Describe how the PAP(s) are deployed. Do you provide a single PAP or must policies be individually managed on each Policy Decision Point (PDP)?
SHOULD provide a single point of policy management 72
See: WIRFPSpecs.xls
© 2007 Board of Regents of the University of Wisconsin System
We developed an evaluation methodology
Evaluation Definition Score
No SupportNo support according to the ratings guidance. No documentation. Extension to meet requirement is difficult, extremely expensive, or not possible to extend.
0
Partial SupportPartially supported, with some aspects missing according to the ratings guidance or the answer doesn't follow expected format. Lacking clear or specific documentation. Unreasonable, or somewhat expensive to extend.
1
Strong SupportMostly supported, with a couple aspects missing according to the ratings guidance. Somewhat well documented in the vendor response with reference to technical documentation. Provides functionality out-of-the-box or easy to extend to provide functionality.
3
Full SupportCompletely supported according to the rating guidance. Fully or somewhat documented in the vendor response with reference to technical documentation. Requirement requires standard expertise to implement, perform, or meet.
9
© 2007 Board of Regents of the University of Wisconsin System
We sent it out, received the responses and scored them
© 2007 Board of Regents of the University of Wisconsin System
And the winner is…..
© 2007 Board of Regents of the University of Wisconsin System
Where do we go from here?
© 2007 Board of Regents of the University of Wisconsin System
Questions?
© 2007 Board of Regents of the University of Wisconsin System
top related