Lualdap fails to set unicodepwd

You can search for lualdap from the Internet, and you will be happy to test, connect, query, add user, ou, and modify the attributes. You cannot change the password unicodepwd. the result of the heavy sacrifice of Google's big law is not confusing. I think the problem is serious when I discuss it online. I found that the certificate, TLS/SSL, ASN.1 BER, and so on are involved. I am angry about modifying a broken password. one by one according to the requirements of the, or report DSID-031A0FC0 error, served.

It seems that you have to start from the beginning and start to re-compile lualdap. From the API step by step, it does not work.

Download a lualdap source code, write a BKL file, compile the file, and then click Next.

Or sanjianke, BKL, bkgen, bat

Lualdap. BKL

<?xml version="1.0"?><makefile><include file="presets$(DIRSEP)simple.bkl"/><option name="WXLUA_DIR" category="path"/><!-- option path --><option name="LUA_DIR" category="path"/><!-- path --><set var="ROOT_DIR">..</set><set-srcdir>$(ROOT_DIR)$(DIRSEP)src</set-srcdir><set var="OUTPUT_PROFIX"><if cond="FORMAT=='mingw'">gcc_dll</if></set><set var="BUILDDIR">$(ROOT_DIR)$(DIRSEP)lib$(DIRSEP)$(OUTPUT_PROFIX)</set><set var="BINDIR">$(ROOT_DIR)</set><dll id="lualdap" template="simple"><define>WINLDAP</define><!-- include --><include>"$(LUA_DIR)$(DIRSEP)src"</include><sources>$(fileList('*.cpp'))</sources><sources>$(fileList('*.c'))</sources><ldflags>-Wl,--enable-auto-import $(SRCDIR)$(DIRSEP)lualdap.def</ldflags><sys-lib>lua5.1</sys-lib><sys-lib>wldap32</sys-lib><dirname>$(BUILDDIR)</dirname><lib-path>$(WXLUA_DIR)\lib\gcc_dll</lib-path><dllname>lualdap</dllname></dll></makefile>

Lualdap. bkgen

<?xml version="1.0" ?><!-- $Id: lualdap.bkgen, v1.0 2010/11/1 14:12:03 $ --><bakefile-gen xmlns="http://www.bakefile.org/schema/bakefile-gen"><input>lualdap.bkl</input><add-formats>mingw</add-formats><add-flags formats="mingw">-o$(INPUT_FILE_DIR)/makefile.gcc</add-flags>  <add-flags>-DWINLDAP -DBUILD=release</add-flags><add-flags>-DLUA_DIR=$(envvar("lua"))</add-flags></bakefile-gen>

Bakeit. bat

clsbakefile_gen --desc=lualdap.bkgen mingw32-make -f makefile.gcc cleanmingw32-make -f makefile.gcc COMSPEC=%comspec% WXLUA_DIR="%wxlua%" LUA_DIR="%lua%" allcopy ..\lib\gcc_dll\lualdap.dll ..\test

I found several articles about this issue,

The first article describes in detail how to generate a qualified unicodepwd (there are too many differences with the descriptions on msdn, and msdn is actually a fool ).

1.Http://technet.microsoft.com/en-us/magazine/ff848710.aspx

The second article describes in detail how to use the ldifde tool to import LDF files with unicodepwd.

2.Http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-ad/20168/LDIFDE-Error-when-trying-to-change-passwords

The third article is a bit comprehensive. The first two articles

3. http://www.nonhostile.com/howto-format-unicodepwd-ldif-active-directory.asp

Note that the ldifde command carries the-H parameter. The unicodepwd is followed by the: In the LDF file. Note that it is not a single colon.

c:\csv:lidfde -i -h -f changpass.ldif -j c:\csvHere is the content of my ldif filedn: CN=testuser,OU=testOU,DC=domain,DC=localchangetype: modifyreplace: unicodePwdunicodePwd::IgBwAGEAcwBzAHcAbwByAGQAIgA=-

4.Http://msdn.microsoft.com/en-us/library/aa366105 (V = vs.85). aspx

5. http://msdn.microsoft.com/en-us/library/Aa367033

The supervisor finds that it does not import functions such as SASL and SSL. Only some init, connect and bind functions. Why is it that the built-in tool can use unicodepwd so easily (it seems that you can modify it With ADSI), but there are so many restrictions on using LDAP.