[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Ldapsearch returning incorrect value

To: openldap-software@OpenLDAP.org
Subject: Re: Ldapsearch returning incorrect value
From: Karsten Gorling <kgorling@physik.tu-berlin.de>
Date: Mon, 26 Sep 2005 17:04:45 +0200
Content-disposition: inline
In-reply-to: <3E3D8ACB1917BD48A27F853F9C4AC79D594050@xmb-blr-412.apac.cisco.com>
References: <3E3D8ACB1917BD48A27F853F9C4AC79D594050@xmb-blr-412.apac.cisco.com>
User-agent: Mutt/1.5.6+20040907i

* Rohit Kumar (rokumar) <rokumar@cisco.com> [050926 16:54]:
> The value returned is as follows:
> MTI4OTMxODIgIA==  
> while the actual value is 12458

The LDAP-utitilities are not internationalized and so return always the
Base64-encoded value as saved in the server. Base64-encoding is for
numbers usually not necessary. How is the attribute "slot" defined?

Ah short hack, to show the base64-decoded Value is

perl -MMIME::Base64 -e 'print decode_base64("YOURSTRING"),"\n"'

-- 
Max-Born-Institut (MBI)/Max-Born-StraÃe 2A/12489 Berlin/Karsten Gorling
Telefon: ++49 30 6392 1341 / Telefax: ++49 30 6392 1309 
E-Mail: kgorling@physik.tu-berlin.de or gorling@mbi-berlin.de
Instantmessenger: Jabber: grafzahl@jabber.fsinf.de or ICQ: 95492828
PGP-Fingerprint:  4BEF 23EA 02AE BACA 9918  31FF 285B 0426 0E1A B2FC
----------------- > encrypted E-Mail preferred <------------------------

Follow-Ups:
- Re: Ldapsearch returning incorrect value
  - From: Howard Chu <hyc@symas.com>

References:
- Ldapsearch returning incorrect value
  - From: "Rohit Kumar \(rokumar\)" <rokumar@cisco.com>

Prev by Date: Ldapsearch returning incorrect value
Next by Date: Re: Ldapsearch returning incorrect value
Index(es):
- Chronological
- Thread