| 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
01/18/2005

  • Project Status
    • “ndsd” still crashing about once a week or so; finally have the Novell “5 incident’ contract in place – will create an “incident” this week.
    • Have access to HR EPM (ERP datawarehouse) tables for getting employee information after go-live.  Switched from using the HR EPM data to using Ron’s “native” daily HR extract, since it comes directly from HR production data, not the EPM.
    • New attributes & their stories: fsuEduCrypt, fsuEduSha1, fsuEduHRConfidential, fsuEduPreferredCN, fsuEduPSHRpayLocation, fsuEduPSHRdeptName, fsuEduPSHRexpireDate
    • Modified Win AD directory attribute script to use newer PSHR fields; added “FSUID = name” into “Company” field.
    • College of Human Sciences eDir impact: connected “chslabs.chs.fsu.edu” WinAD DC to eDir; associated a slew of existing accounts; writing once-a-day-script to manage (auto create/disable) CHS WinAD accounts from FSUID information.
    • Have made some progress with manipulating users on the BlueSocket boxes; a meeting will be set soon to plan with Sherry & Clint what can be done with eDir and the BlueSocket boxes.
    • Meeting later today to see what BusObj FSUID/group authentication needs are and how the eDir can be used to meet those needs.
    • Meeting later this week to discuss technical and non-technical ramifications of moving FSUID and Secure Login pages under Blackboard.
    • Major concern: shortening the lag for new accounts:

1. Get an FSUCard at the FSUCard Center (http://www.fsucard.fsu.edu/).

2. Wait for up to a day for the data to flow from the FSUCard system to UCS/CARS.

3. Go to the CARS web site (https://cars.acns.fsu.edu/CARS/new_accounts.html) and sign up for your CARS account.

4. Wait up to four hours for the CARS data to go to the FSUID server.

5. Go to the FSUID web site (http://fsuid.fsu.edu) and set your FSUID password.

6. Wait a day for the FSUID information to go to OMNI (list of new employees).

    1. Get LDAP authentication working under AIX 5.2 (either natively using secldapclntd or using open source packages) – thanks to UCS for providing access to aim1.acns.fsu.edu for AIX testing.  Have made some progress on this; need to continue moving forward.
    2. Get LDAP authentication & attribute updating working with UCS-configured BlueSocket box (thanks to UCS for providing the box!).  Have made some progress on this; need to continue moving forward.
    3. Continuing to provide CARS user functions in FSUID –Waiting on a “CARS API” via an SSH tunnel and Oracle PL/SQL calls for CARS account management (Breeze is writing the PL/SQL calls)
    4. Learn how to render FSUID pages in a native Blackboard module.  Build an openldap public search engine.
    5. Provide an option for departmental creation of visitor accounts and AD Exchange accounts with appropriate associations (College of Medicine).
    6. Write web-based documentation explaining how to use eDir for authentication (pure LDAP, UNIX passwd file, RADIUS, Apache auth_ldap, etc.).
    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.  Secure Login beginning to use FSUSN in place of SSN.  FSUID now offers FSUCard/FSUSN as a possible authentication method.
| florida state university |