| fsu torches | | florida state university |
  FSUID Home > Project Documentation > History > Technical Meetings > Outline | Home | Search | Help | Contact || Home || Search || Help || Contact |

 



References

LDAP/eDir Documents
LDAP
Windows AD LDAP Schema
 
 
Metadirectory Technical Status Meeting
https://fsuid.fsu.edu/admin
11/02/2004

  • Project Status
    • Associated a slew of COM AD accounts to FSUIDs using a one-time load.
    • Now populating fsuEduCarsFsucardType1 (see http://devfsuid.fsu.edu/admin/fsuid_descript/fsu-edu-cars-fsucard-type1.html) from the infamous FSUCARD/HRMS crossover file).
    • Discuss moving http://fsuid.fsu.edu web pages under a portal, to align with the University’s desire to implement an enterprise portal and redo the FSU home page – seems that either a standalone Blackboard instance, PeopleSoft portal or a uPortal instance are some logical choices to use.
    • Discuss multiple “E” records in CARS and how that affects FSUIDs (e.g., “natec” & “slawlor” example).
    • Added a Helpdesk option to “Rename this FSUID” iff card type == 18 and FSUID is all numeric.  Added support for handling of card type == 18 and all numeric FSUID in Secure Login (rename FSUID using the “email address” algorithm for alumnus).
    • Working integration issues with Secure Login (“Manage Login Information” link within SL ßà FSUID web page); will have a redirect URL/FSUID scheme (eventually this will be done seamlessly via CAS).
    • Continuing to provide CARS user functions in FSUID –Working on a “CARS API” via an SSH tunnel and Oracle PL/SQL calls for CARS account management.
    • Next Big Event for FSUIDs: “go live” of PeopleSoft HR in mid-December.  Will need to make sure an HR extract from PS is available as it is today from HRMS to continue to feed the eDir with employee identities.
    • Switched eDir master node from udbprod back to mdsoti.fsu.edu.  Tweaked some memory cache parameters (from dynamic to static) to make “ndsd” more reliable; keeping an eye on it (memory monitor script running).  Interesting to note FSUID web server usage post 10/15: https://fsuid.fsu.edu/usage/usage_200410.html
    • Note email/event archive at http://devfsuid.fsu.edu/admin/project-history/.
  • Action Items
    1. [IS, ODDL] Connect C.A.S. to Secure Login, Blackboard & FSUID, all pointing to eDir.
    2. Continue to write equivalent functionality of CARS user functions at https://cars.acns.fsu.edu/CARS/account_maintenance.html into the FSUID pages.  Develop two way reliable CARS ßà FSUID “RPC” mechanism (needed to eliminate the CARS à FSUID “load lag” and to provide all CARS user functions in FSUID).
    3. Need to develop “departmental Helpdesk” user management pages and a “departmental super user” LDAP account for departmental use using dynamic LDAP group ACLs (Film School is still very interested)
    4. [UCS, IS] Integrate FSUID management closer to CARS (e.g., when person activate or changes CARS password or user name, immediately change it in the eDir!) NOTE: this process may be subsumed by FSUID equivalency.
    5. [IS] Write web-based documentation explaining how to use eDir for authentication (pure LDAP, UNIX passwd file, RADIUS, Apache auth_ldap, etc.).
    6.  [IS] Test and install new Perl “LDAP failover” module; get mod_perl working on fsuid.fsu.edu.
    7. [Group – longer term] Continue working SSN à FSNSN replacement discussions with campus.  Pushing in IS out to customers to start using FSUSN which is now populated in USER_ACCOUNT.
    8. Populate/associate Novell account information into eDir (need to get with User Services)
| florida state university |