Changes between Version 8 and Version 9 of Phase1Planning


Ignore:
Timestamp:
07/13/12 10:55:03 (12 years ago)
Author:
dabantz@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Phase1Planning

    v8 v9  
    4343'''Task details''' 
    4444 
    45 1. Install and configure Grouper (including relevant components) and integrate with their subject sources. 
     451. Install and configure Grouper (including relevant components) and integrate with their subject sources.[[br]] 
     46 ''Each step documented in detail as source and/or narrative in the IAM wiki.'' 
    4647 
    47 - Install the Grouper API and Grouper UI components. 
    48 - Disable default grant read/view access on new group creations.  This is generally good practice so that read/view access has to be explicitly given. 
    49 - Enable wheel group to allow a group of admin users. 
    50 - Enable include/exclude and requireGroup configurations.  This allows easier creation of composite groups. 
    51 - Enable the Grouper Report to run daily.  What email address should the report be sent to? 
    52 - Enable membership import and export in the Grouper admin UI. 
    53 - Configure the subject API to query subjects from the production LDAP. 
     48* Install the Grouper API and Grouper UI components. 
     49* Disable default grant read/view access on new group creations.  This is generally good practice so that read/view access has to be explicitly given. 
     50* Enable wheel group to allow a group of admin users. 
     51* Enable include/exclude and requireGroup configurations.  This allows easier creation of composite groups. 
     52* Enable the Grouper Report to run daily.  What email address should the report be sent to? 
     53* Enable membership import and export in the Grouper admin UI. 
     54* Configure the subject API to query subjects from the production LDAP.[[br]] 
     55  
    5456 
    5557 
    … …  
    6062''ePPN is built in the IdP from UA Username'' 
    6163 
    62 3. Set up jobs to load data into Grouper from LDAP. 
     643. Set up jobs to load data into Grouper from LDAP.[[br]] 
     65 ''Each step documented in detail as source and/or narrative in the IAM wiki.'' 
    6366 
    6467- Set up the Grouper Loader to load buildings into Grouper under ua:inst:buildings using data from the production LDAP. 
    … …  
    6669''May as well generate all building-based groups; standard officeLocation attribute in LDAP is populated with a room number and [[https://iam.alaska.edu/grouper/raw-attachment/wiki/Phase1Planning/buildingcodesnamescampus.xlsx|controlled vocabulary building abbreviation]], though there are a small number exceptions generated by individuals entering a building name in the room designator entry field instead of choosing from the pre-populated list of buildings.'' 
    6770- Are the values of the attribute the exact name to use as the Grouper groups?  Or does there need to be some mapping or parsing done? 
    68 ''Need to strip pre-pended room designation; may wish to include campus in the group name'' 
     71''Need to strip pre-pended room designation; should probably include campus in the group name; list of buildings with short and full name and campus is attached.'' 
    6972- How often should the job run?  Hourly?  Daily?  Probably depends on how long it takes to run the LDAP query and how many users there are. 
    7073