davical/testing/tests/ldap/0006-test-DN-in-Groups.result
Andrew Ruthven c273b38234 Test adding non-existant LDAP user to a group
This is to tickle my suspicion of the bug as reported by Thorsten Marquardt
in https://sourceforge.net/p/davical/mailman/message/58766531/ with this
error message reported:

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

You need to look in 3da860e5d5e732c2dedb62a73c76608a2b7098a4 for that line
number as I've just made some improvements to the code.

I have also improved the SQL to check if the users have been added, and
discovered that the result file *did not* have them. This test was failing
due to the test config file looking for memberUid, not member. Also, fix
that.
2024-05-01 22:32:33 +12:00

130 lines
3.0 KiB
Plaintext

HTTP/1.1 207 Multi-Status
Date: Dow, 01 Jan 2000 00:00:00 GMT
DAV: 1, 2, 3, access-control, calendar-access, calendar-schedule
DAV: extended-mkcol, bind, addressbook, calendar-auto-schedule, calendar-proxy
ETag: "da739b6b98d20b87833748d890466cde"
Content-Length: 946
Content-Type: text/xml; charset="utf-8"
<?xml version="1.0" encoding="utf-8" ?>
<multistatus xmlns="DAV:">
<response>
<href>/caldav.php/</href>
<propstat>
<prop>
<resourcetype>
<collection/>
</resourcetype>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
<response>
<href>/caldav.php/resource1/</href>
<propstat>
<prop>
<resourcetype>
<collection/>
<principal/>
</resourcetype>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
<response>
<href>/caldav.php/resource2/</href>
<propstat>
<prop>
<resourcetype>
<collection/>
<principal/>
</resourcetype>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
<response>
<href>/caldav.php/gON_ldap1/</href>
<propstat>
<prop>
<resourcetype>
<collection/>
<principal/>
</resourcetype>
</prop>
<status>HTTP/1.1 200 OK</status>
</propstat>
</response>
</multistatus>
SQL Query 1 Result:
active: >1<
email: >gON_ldap1@example.com<
fullname: >gON LDAP 1<
last_used: >NULL<
password: >NULL<
username: >gON_ldap1<
active: >1<
email: >gON_ldap2@example.com<
fullname: >gON LDAP 2<
last_used: >NULL<
password: >NULL<
username: >gON_ldap2<
active: >1<
email: >gON_ldap3@example.com<
fullname: >gON LDAP 3<
last_used: >NULL<
password: >NULL<
username: >gON_ldap3<
active: >1<
email: >gON_ldap4@example.com<
fullname: >gON LDAP 4<
last_used: >NULL<
password: >NULL<
username: >gON_ldap4<
active: >1<
email: >NULL<
fullname: >gON_ldap_group1<
last_used: >NULL<
password: >NULL<
username: >gON_ldap_group1<
active: >1<
email: >NULL<
fullname: >gON_ldap_group2<
last_used: >NULL<
password: >NULL<
username: >gON_ldap_group2<
active: >1<
email: >NULL<
fullname: >gON_ldap_group3<
last_used: >NULL<
password: >NULL<
username: >gON_ldap_group3<
active: >1<
email: >NULL<
fullname: >gON_ldap_group4<
last_used: >NULL<
password: >NULL<
username: >gON_ldap_group4<
SQL Query 2 Result:
group_name: >gON_ldap_group1<
users: >gON_ldap1<
group_name: >gON_ldap_group2<
users: >gON_ldap1, gON_ldap2, gON_ldap4<
group_name: >gON_ldap_group3<
users: >gON_ldap1, gON_ldap3<
group_name: >gON_ldap_group4<
users: >NULL<