This is most related to architecture than LDAP itself, and is exactly what I've been doing in my current position. You have to decide wich of your user directories will be the main one. In our case was the HHRR app wich imposed an oracle solution. With sql triggers we create the user in our LDAP and then the rest of our apps rely only on LDAP queries. We also have several tasks to synch systems without a direct LDAP connection, like old mysql based apps. This scheduled tasks (usually running at night) dumps the entire directory, check for updates and modify the destination system. If you need more details about some specific task don't hesitate to ask. abosch ----- Missatge original ----- > De: "Andy Spooner" <andy.spooner@xxxxxxxx> > Per: 389-users@xxxxxxxxxxxxxxxxxxxxxxx > Enviats: Dimarts, 3 de Novembre 2015 19:32:44 > Assumpte: DB account master integrated with LDAP > > > > I am using ldap to share user account information across two > applications. Is it possible to using 'Application 1' as the central > reference instead of the LDAP server? E.g. Application 1’ holds and > maintains account information, which updates ldap periodically. > 'Application 2' will look up LDAP for account informations. > 'Application 1’ is the main system and will hold millions of > accounts which would operate quicker from the DB without having to > refer to LDAP for usernames, passwords, etc. ‘Application2’ will > require a small subset of users to logon using credentials of users > in the master database – which can be done via LDAP. > -- > 389 users mailing list > 389-users@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/389-users -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
