Different "userPassword" format in an LDIF file

[paul_si...@mail.com]

When exporting as an LDIF file with eDirectory, I get the following
format for the userPassword attribute:

userpassword: {SHA}TyCcjdiYBjVyo3PYWSmSn+Q4JXY=

When do the same action using an LDAP client (JXplorer), I get this
format:

userpassword:: e1NIQX1UeUNjamRpWUJqVnlvM1BZV1NtU24rUTRKWFk9

Why is there a difference?

Paul

[Jim Henderson]

One is Base64 encoded, one isn't. The one that is is the latter, the
double "::" is an indicator that this has been encoded.

When I run the second string through (without the "userpassword:: " text),
I get the first one.

Jim

--
Jim Henderson, CNA6, CDE, CNI, LPIC-1
Novell Training Services

[paul_si...@mail.com]

Indeed. Thanks a bunch.

Paul

[Marcel Cox]

I don't really see why you would need to recreate your users just to add
some missing attributes. UniqueID and other attributes can be added using
various mechanisms.

--
Marcel Cox
http://support.novell.com/forums

[Marcel Cox]

Check the following article:

http://www.novell.com/coolsolutions/tip/17303.html

and the following TID:

https://secure-support.novell.com/KanisaPlatform/Publishing/866/3110036_f.SAL_Public.html

[Peter Kuo]

No, you can't -- to export UP, you need to use NMAS's LDAP-specific API
which is not in normal utils.

--

Peter
eDirectory Rules!
(ssAegis powering up to 65% ...)

[Peter Kuo]

Pawel Janowski wrote:

> Such export should be possible with ICE. But I can't get encrypted
passwords in output LDIF file.

No, you can't use ICE for it -- you need a custom app. How many users are
you talking about?

[Peter Kuo]

UniqueID is generally the same as CN, so you can do some simple script
file manipulation to work that out.

[Jim Willeke]

You might want to look at this CoolTool
http://www.novell.com/coolsolutions/tools/18609.html
-jim

Peter Kuo wrote:
> If stored as Simple Password that could be what you see -- if stored as
> hashed.
>