Changes between Version 2 and Version 3 of SoWPhases


Ignore:
Timestamp:
06/22/12 15:05:07 (12 years ago)
Author:
dabantz@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SoWPhases

    v2 v3  
    88Work to be done: 
    99 
    10 • Deploy a working instance of Grouper;  
    11  ( "working" entails an instance tested and accepted for these PoC functions, but not reduncant platform with active monitoring required for production) 
    12 • Provide authentication and authorization to Grouper via UA-standard SAML IdP, verifying users with UA-Username & AD password 
    13 • Create building-based groups within LDAP, and  
    14 • Implement a process for automatically provisioning users into the appropriate group(s) based on the office location data in their LDAP record 
    15 • Create ad hoc groups of allowed VPN users within LDAP, and  
    16 • Implement a process and end user interface for provisioning individual users into one or more such groups 
    17 • Verify that group membership lists and groups to which and individual belongs are both consumable via LDAP queries 
    18 • Document all configurations, interfaces, and connectors 
    19 • Train IAM as needed on maintenance and operation of Grouper, connectors, and interfaces 
     10• Deploy a working instance of Grouper; ( "working" entails an instance tested and accepted for these PoC functions, but not reduncant platform with active monitoring required for production)[[BR]] 
     11• Provide authentication and authorization to Grouper via UA-standard SAML IdP, verifying users with UA-Username & AD password[[BR]] 
     12• Create building-based groups within LDAP, and [[BR]] 
     13• Implement a process for automatically provisioning users into the appropriate group(s) based on the office location data in their LDAP record[[BR]] 
     14• Create ad hoc groups of allowed VPN users within LDAP, and [[BR]] 
     15• Implement a process and end user interface for provisioning individual users into one or more such groups[[BR]] 
     16• Verify that group membership lists and groups to which and individual belongs are both consumable via LDAP queries[[BR]] 
     17• Document all configurations, interfaces, and connectors[[BR]] 
     18• Train IAM as needed on maintenance and operation of Grouper, connectors, and interfaces[[BR]] 
    2019 
    2120Conditions: 
    2221 
    23 UA IAM will provide the accounts and access permissions to its systems required for this work. 
     22UA IAM will provide the accounts and access permissions to its systems required for this work.[[BR]][[BR]] 
    2423Unicon will document efforts and expenses and UA IAMI will approve monthly billed hours of consulting based on progress and receipt of work. 
    2524Any travel or other expenses will be approved in advance and must conform to UA policies on travel and expenses. 
    … …  
    3433Work to be done in Phase II: (?) 
    3534 
    36 • Document the existing database structure of ZUAUSR and replicate the functionality in Grouper's database schema 
    37 • Document a sub-set of existing ZUAUSR interfaces (Oracle FORMS) used for requesting and granting permissions and roles 
    38 • Design the connector needed for Grouper to use legacy identities from Banner (which the existing in-house tool uses as user identities) or some means of mapping standard UA identities to those legacy identities 
     35• Document the existing database structure of ZUAUSR and replicate the functionality in Grouper's database schema[[BR]] 
     36• Document a sub-set of existing ZUAUSR interfaces (Oracle FORMS) used for requesting and granting permissions and roles[[BR]] 
     37• Design the connector needed for Grouper to use legacy identities from Banner (which the existing in-house tool uses as user identities) or some means of mapping standard UA identities to those legacy identities[[BR]] 
    3938• Implement user interfaces used for roles for the Document Imaging application, and configure Grouper database and rules to enable Grouper end users to provision those roles as Groups with membership attribute (isMemberOf) values currently consumed by the OnBase Digital Document application (that is, replicate the existing functionality of granting roles used by this application, using the same LDAP directory currently used) 
    4039