|
From: Thorsten M. <Mar...@ko...> - 2024-05-02 08:24:45
|
Hi Andrew, this looks great now. But it would be great to have a kind of "dry run sync" to avoid to have many "false" items in database due to erroneous ldap filter settings. We use davical for several years now and it's a very wellcome resource for us. Till my next question Thorsten Am 30.04.24 um 15:47 schrieb Thorsten Marquardt via Davical-general: > Moin Andrew, > > first of all: Thank you for your efforts. This topic is not time > critical and I/we can live without Group sync. But it would be great to > have it working ;-) > > I can do the next tests earliest in two day. > > > Kind regards > > Thorsten > > > Am 30.04.24 um 15:33 schrieb Andrew Ruthven: >> Hi Thorsten, >> >> On Tue, 2024-04-30 at 11:02 +0200, Thorsten Marquardt via Davical-general >> wrote: >>> But I stll get the LDAP exception >>> >>> Exception [0] ldap_get_attributes(): Argument #2 ($entry) must be of >>> type LDAP\ResultEntry, false given >>> At line 718 of /usr/share/davical-master/inc/drivers_ldap.php >> I've written a test which tickles this issue. It looks to me like you may >> have a user in an LDAP group which doesn't exist; or, your users are stored >> in your LDAP groups in another way that I haven't encountered yet! >> >> I've modified the drivers_ldap.php to log this and move onto the next >> record. >> >> In the process I've also fixed a couple of other bugs I've found. >> >> I've created a MR for this change, you can see it here: >> https://gitlab.com/davical-project/davical/-/merge_requests/138 >> It is rather late where I live, so I'm off to bed, and will hopefully be >> able to merge this in the morning. >> >> Thank you for reporting this bug, >> Andrew >> > > > _______________________________________________ > Davical-general mailing list > Dav...@li... > https://lists.sourceforge.net/lists/listinfo/davical-general |