| 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
8/31/2004

  • Project Status
    • Upgraded eDir software from 8.7.1.2 to 8.7.3.1 (plus two more patches) on “mdsacns” (all five production eDir servers are now at latest patch level).
    • Added an abbreviated version of student class schedules from various NWRDC DB2 tables into “fsuEduStuSchedule” (ex: https://devfsuid.fsu.edu/helpdesk); doing a “proof of concept” FSUID version of the ever-popular “Student Locator” app.
    • Added another “fsuEduWebApps” named “fsuvpn” & set up freeRADIUS on mdsoti.fsuedu for User Services; added  “FSUID web applications” to personal tab (ex: https://devfsuid.fsu.edu)
    • Modified how “fire2” aliases are displayed to better match reality (ex: https://devfsuid.fsu.edu)
    • Automated “modifyADAttributes.pl” (pushes eDir directory info back to associated Outlook accounts in Exchange)
    • Updated public search to include students, using same criteria as on www.fsu.edu search engine (ex: https://devfsuid.fsu.edu/search).
    • Getting ready to migrate IS Secure Login to use “native” FSUID and eDir, rather than ldap2 (http://admin-c6140-10.uc.fsu.edu:8080/SecureLogin)
    • Figured out how to generalize Windows Active Directory account associations to include ANYAD domain controller that wants to “play” (e.g., connecting the “ad.fsu.edu” trees, such as “med.ad.fsu.edu”) – also want to create an “associate Outlook account” that could be done either by an individual with password challenge or by the Helpdesk utility).  Can offer to push directory back to AD DCs, if wanted (see https://devfsuid.fsu.edu/admin/lib/WinADLDAPAttributes.html).
  • Action Items
    1. Talk briefly about old request from a Tom Welsh – he wants the password check algorithm to allow a non-alphanumeric to BEGIN the password; apparently the algorithm we now use requires the non-alpha to be somewhere other than the 1st char...anybody have a problem with this?
    2. Talk briefly about multitude of flags in student records (https://devfsuid.fsu.edu/admin/fsuid_descript/fsu-edu-stu-privacy-flag.html) & how they might relate to the various FSUID applications
    3. Populate/associate Novell account information into eDir (still need a Novell proxy admin account; have used my personal Novell account for some initial LDAP browsing)
    4.  [IS] Set up “Outlook account enabler” web page (done) and have OTI create new FSU AD accounts disabled by default (this will force Outlook ßà FSUID associations)  (have new Helpdesk option for now, but perhaps this should be front-burnered?)
    5. [IS] Write web-based documentation explaining how to use eDir for authentication (pure LDAP, UNIX passwd file, RADIUS, Apache auth_ldap, etc.)
    6. [UCS, IS] Integrate FSUID management closer to CARS (e.g., when person changes CARS password or user name, immediately change it in the eDir!)
    7. [IS] Write Perl “LDAP failover” module; get mod_perl working on fsuid.fsu.edu.
    8. [IS] Re-design CARS pages to match look & feel of FSUID pages.
    9. [IS, ODDL] Connect C.A.S. to Secure Login, Blackboard & FSUID, all pointing to eDir.
    10.  [Group – longer term] Continue working SSN à FSNSN replacement discussions with campus & design “FSUSN” algorithm (have a working password algorithm; now need to populate FSUSN in eDir and in USER_ACCT), then write fsuid “view” page for “consumers”)
| florida state university |