directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "CG Monroe (JIRA)" <>
Subject [jira] [Created] (DIRSERVER-1776) Photo and Jpegphoto attributes store corrupt data/Generate Syntax Errors
Date Fri, 07 Dec 2012 16:13:21 GMT
CG Monroe created DIRSERVER-1776:

             Summary: Photo and Jpegphoto attributes store corrupt data/Generate Syntax Errors
                 Key: DIRSERVER-1776
             Project: Directory ApacheDS
          Issue Type: Bug
          Components: ldap
    Affects Versions: 2.0.0-M8, 2.0.0-M7
         Environment: Windows 7 / Win Server 2003
            Reporter: CG Monroe
            Priority: Blocker

I've been using M3 for a while but decided to use M7 (this started before M8 released) for
a new site.  With M3, our PhP access code could store and retrieve photo's from the photo
attribute.  With M7, any updated image came back corrupt and a larger size.

Updated to M8 and still had same problem.

Verified it was not the my code's fault by using phpldapadmin web tool and doing some testing
with Apache Dir Studio.  In most cases, the data gets corrupt or in the case of the jpegphoto
attribute gets a syntax error on save.  The one exception is that Studio's jpegphoto attribute
value handling worked.

The easiest way to duplicate this in Studio is to do the following:

- Add a photo attribute to a user.
- Load an image into this via the hex editor
- OK to add to attribute/value.

Note that the data size is larger than original

- Edit attribute and save data to different image file.

Image is corrupt.

An alternative test is to have a good LDIF export (like one from M3 which works) that contains
an image attribute. 

Import and Export the LDIF file and compare.  (note, jpegphoto attributes will generate a
syntax error).

Note all this testing has been done within a Windows environment... don't know if this is
related or not... but with binary data, it should not matter.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message