** This post is pretty incomplete, I gave up on it. But there is enough info here that may be usefull**
eDirectory has several attributes for photos, here are the raw schema attributes from an eDirectory install from iMonitor. An interesting note is that ldapPhoto and photo have the same OID. Because the syntax is Octet String I think that the photos can be stored as either Binary Data or as a Base64 encoded representation of the image.
Used By Class
|jpegPhoto||Sync. Immediate||Octet String||0||4294967295||0.9.2342.19200300.100.1.60||User|
|ldapPhoto||Sync. Immediate||Octet String||0||4294967295||0.9.2342.19200300.100.1.7||User|
|photo||Sync. Immediate||Octet String||0||4294967295||0.9.2342.19200300.100.1.7||Person|
Using and populating these attributes can be tricky. If you use Identity Manager, the User Application stores pictures in the photo attribute.
2.6. JPEG Photograph
Used to store one or more images of a person using the JPEG File
Interchange Format [JFIF].
DESC 'a JPEG image'
SYNTAX 22.214.171.124.4.1.14126.96.36.199.28 )
Note that the jpegPhoto attribute type was defined for use in the
Internet X.500 pilots but no referencable definition for it could be
On recomended way to import photos is to use an LDIF.
This seems to work if you can’t / don’t want to base64 encode the values into the LDIF.