Bug 688427 - ldif2db import of ldif truncates base-64 attributes such as jpegPhoto
Summary: ldif2db import of ldif truncates base-64 attributes such as jpegPhoto
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: 389
Classification: Retired
Component: Database - Import/Export
Version: 1.2.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Noriko Hosoi
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-17 01:04 UTC by Steven Seed
Modified: 2015-01-04 23:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-17 07:52:21 UTC


Attachments (Terms of Use)

Description Steven Seed 2011-03-17 01:04:38 UTC
Description of problem:

When importing an ldif file containing base-64 encoded jpegPhoto or even when using the '< file:/' notation for the attributes, the resulting jpegPhoto attribute is truncated to one line. 

Version-Release number of selected component (if applicable):
389-ds 1.2.1-1 on RHEL 5.5

How reproducible:
Always


Steps to Reproduce:
1. Create a ldif file with entries containing jpegPhoto attributes which are base-64 encoded or contain a file path to a jpeg file.
2.use the ldif2db utility to import data into a new basedn
  
Additional info:
I am able to directly import the same ldif data using ldapmodify -a directly without running into the problem. It seems to only happen when using ldif2db which does a atomic import of the data using the extensibleObject method.

I can provide sample ldif data if necessary.

Comment 1 Steven Seed 2011-03-17 07:52:21 UTC
After further testing, I have been able to get my imports working. It appears there was some formatting problems with my ldif file that was causing the import to fail. I'm now properly formatting my ldif file.


Note You need to log in before you can comment on or make changes to this bug.