Date: Thu, 28 Mar 2024 19:25:23 +0000 (UTC) Message-ID: <1864695637.6861.1711653923161@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6860_1542027212.1711653923159" ------=_Part_6860_1542027212.1711653923159 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Why are we doing this? Our Information Technology management has been seeking an automated proces= s to provision and deprovision entities based upon organizational data stor= ed primarily in our Banner ERP system. An initial attempt at this was inade= quately resourced, and was not seeded with a breadth of university executiv= e stakeholder involvement, so it did not successfully achieve its desired m= ission. Our active involvement in the InCommon CSP cohort represents a rene= wed effort to approach the original goal in a staged, and better supported = manner. |
Problem Statement: We = are in the process of seeking for a better solution to enhance our current = Identity and Access Management system. Impact Statement: One of our IT goals is to prioritize and adjust services to impr= ove the customer experience, by increasing availability, reliability and su= stainability, leading to a more responsive and enhanced information technol= ogy. |
How do we judge success? Success metr= ics |
When the Grouper data has been shown to be a = close equivalent of the legacy solution, initial success will be declared. = For example,
|
What are possible solutions? | Grouper and Midpoint
|
High-level timeline | Project Phase Milestone Completion Dates
|
Issues tracking | A traditional approach to tracking will in= clude an issues log, with assigned responsible individual (or specific team= ) designated to resolve. |
Who is the customer and how does this he= lp them? | Our executive director of SSIA has commiss= ioned this effort as an approach to address audit concerns regarding accoun= t and account permission deprovisioning. This will help us to show progress= before the next round of audit. |
Why will the customer want this? | A renewed process for automated role-based= access control (RBAC) has been desired for several years, but a formal eff= ort has not been properly commissioned until our recent involvement in InCo= mmon CSP. |
Scale and scope | For the first phase, resources are dedicat= ed to demonstrate Grouper (and Midpoint) in a functional proof-of-concept. = Once proven, we will commence with a second phase to introduce this process= ing into our production environment. |