jmcneil
Programmer
- Jan 8, 2008
- 3
- 0
- 0
We're hoping to use the Directory Services module (version 3.0 with Livelink 9.7.0) to synchronize select users from an LDAP tree. We're planning on having it be a read only process as we don't want Livelink to update the LDAP tree.
The documentation says that each user who is to be synchronized requires the llserverinfo attribute, but I'm wondering if that is only required for 2 way synchronizations (not read only). It seems as though the search filter provided with the directory services module should be able to handle which users will actually get brought into Livelink.
As for groups I was hoping someone could just confirm my understanding of how they work. I presume that through the group search filter we are able to choose which groups will get pulled into Livelink, and if those groups have an llquery attribute it will be executed and the users that that query returns (and match the user search filter) will be populated in that group.
Does that mean that groups don't need the llserverinfo attribute either? I would think they wouldn't given the existence of the group search filter.
The documentation says that each user who is to be synchronized requires the llserverinfo attribute, but I'm wondering if that is only required for 2 way synchronizations (not read only). It seems as though the search filter provided with the directory services module should be able to handle which users will actually get brought into Livelink.
As for groups I was hoping someone could just confirm my understanding of how they work. I presume that through the group search filter we are able to choose which groups will get pulled into Livelink, and if those groups have an llquery attribute it will be executed and the users that that query returns (and match the user search filter) will be populated in that group.
Does that mean that groups don't need the llserverinfo attribute either? I would think they wouldn't given the existence of the group search filter.
