sergio wrote:
> On 08/15/2012 12:03 AM, Dan White wrote:
>
>>> userPassword:: e1NBU0x9dXNlcm5hbWVAcmVhbG0K==
>
>> Notice the double colons.
> Yes, it shows that the value is base64 encoded.
>
>>> but I'd like to see:
>>> userPassword:: {SASL}username@realm
>
>> Which would not exist here.
> This is my mistake of course, I mean:
> userPassword: {SASL}username@realm
>
>
>> Your value contains a newline character, which is why it is being
>> returned encoded.
>
> Unfortunately you are wrong. This is my bad example. Real values in the
> database have no newline or some other non-ASCII non printable
> characters.
I repeat what I always write in such a case:
If you want to process LDIF then be prepared to process any LDIF data
compliant to RFC 2849. Period.
Best approach is to use a decent LDIF module for your favourite scripting
language.
Ciao, Michael.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature