Bug#704069: davical: ldap user entry attribute 'modifyTimestamp' not correctly mapped to internal attribute 'modified'

2014-12-16 Thread Florian Schlichting
Hi Bernd,

you wrote in Debian bug #704069 (https://bugs.debian.org/704069):

 The davical authentication hook for ldap makes use of drivers_ldap.php
 which is also responsible to sync users from ldap to davical. While
 doing so the timestamp from 'modifyTimestamp' of the ldap entry should
 be used for the internal attribute 'modified'. Unfortunately the
 example configuration in /etc/davical/config.php uses 'mapping_field'
 = array( ..., updated = 'modifyTimestamp', ...) and not 'modified'
 which leads to warnings in apache logs and propably the corresponding
 field not being updated

The file you're talking about is config/example-config.php in git and
currently shipped in the davical Debian package as
/usr/share/doc/davical/examples/davical-conf.php/example-config.php.gz

I've been searching wiki.davical.org a bit, and it seems our LDAP
documentation is a mess. If you're in a position to help us clean that
up, correct misunderstandings and consolidate duplicate information in
one place that would greatly be appreciated!

http://wiki.davical.org/w/Configuration/Authentication_Settings/LDAP_groups
documents 'updated' for the group_mapping_filed array

http://wiki.davical.org/index.php/Synology_DS211
documents 'modified' for mapping_field, and 'updated' for
group_mapping_field

http://wiki.davical.org/w/Configuration_settings
documents 'updated' for mapping_field

http://wiki.davical.org/w/Configuration/Authentication_Settings
documents 'updated' for both mapping_field and group_mapping_field

http://wiki.davical.org/index.php/Configuration/Authentication_Settings/LDAP_Examples
documents 'modified' for mapping_field, and has an interesting comment
at the end of the format_updated array:

'S' = array(12,2)), // map LDAP modifyTimestamp field to SQL updated 
field

http://wiki.davical.org/w/Configuration/Authentication_Settings
has an explanation of the parameters:

mapping_fieldAn array of DAViCal field names vs. their LDAP mappings
group_mapping_field  An array of DAViCal field names vs. their LDAP 
mappings 
format_updated   An array, keyed on Y, m, d, H, M and S with the
 values being arrays of (start,length) for
 substring operations on the DAViCal 'updated'
 field sourced from LDAP. 

Now, I wonder if that field is called 'modified' or 'updated' in
DAViCal, or perhaps it was renamed but not in all places??

(This mail is partly for documentation so others can pick up where I'll
have to leave this issue for now)

Florian


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#704069: davical: ldap user entry attribute 'modifyTimestamp' not correctly mapped to internal attribute 'modified'

2013-03-27 Thread Bernd May
Package: davical
Version: 1.1.1-1
Severity: normal



-- System Information:
Debian Release: 7.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages davical depends on:
ii  debconf1.5.49
ii  libawl-php 0.53-1
ii  libdbd-pg-perl 2.19.2-2
ii  libyaml-perl   0.81-1
ii  php5-pgsql 5.4.4-14
ii  postgresql-client  9.1+134wheezy3
ii  postgresql-client-9.1 [postgresql-client]  9.1.8-1

Versions of packages davical recommends:
ii  postgresql  9.1+134wheezy3

davical suggests no packages.

-- no debconf information

The davical authentication hook for ldap makes use of drivers_ldap.php which is 
also responsible to sync users from ldap 
to davical. While doing so the timestamp from 'modifyTimestamp' of the ldap 
entry should be used for the internal attribute 
'modified'. Unfortunately the example configuration in /etc/davical/config.php 
uses
'mapping_field' = array( ..., updated = 'modifyTimestamp', ...) and not 
'modified' which leads to warnings in apache logs
and propably the corresponding field not being updated


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org