Dear *,
I think I found the solution.
Indeed, you were all right !
The correct command yith the Openldap ldapsearch command is :
ldapsearch -v -h 192.168.122.142 -p 389 -s base -U
dn:uid=fhornain,ou=People,dc=example,dc=com -b dc=example,dc=com -Y
DIGEST-MD5
But you need to have the password
On 10/27/2010 11:35 AM, Orion Poplawski wrote:
It appears that my 389-console is trying to get /java/jars/389-admin-1.1.jar
to access the admin server and /java/jars/389-ds-1.2.3.jar to access the
directory server, but the jar files are in /java/ not /java/jars.
389-admin-1.1.11-1.el5
On 10/27/2010 11:44 AM, Orion Poplawski wrote:
I manually copied over the jars, and now I get:
ClassLoader: :loadClass():name:com.netscape.management.client.util.RemoteImage
ClassLoader:
:loadClass():loading:com.netscape.management.client.util.RemoteImage
ClassLoader:
Orion Poplawski wrote:
Running on CentOS 5.4, get:
type=AVC msg=audit(1288197048.706:347260): avc: denied { execute_no_trans }
for pid=1388 comm=httpd.worker path=/usr/lib/dirsrv/dsgw-cgi-bin/lang
dev=dm-4 ino=225129 scontext=system_u:system_r:httpd_t:s0
