Am Mittwoch 03 November 2010, 09:52:26 schrieb Benjamin Griese:
Hello Ralf,
[..]
In the meantime I set the ACL, but unfortunatly it didn't help solving
the problem, you may take a look at my example:
DN: olcDatabase={1}hdb,cn=config
olcAccess: {0}to attrs=userPassword,shadowLastChange by
Hello Ralf,
thank you very much for your help! :)
In the first place it didn't work and I was sure you have tested the
functionality, so I checked what I may have configured
differently/wrong.
So I checked my list of supportedControls which are presented to the clients:
ldapsearch -x -b -s base
Am Donnerstag 28 Oktober 2010, 19:57:17 schrieb Benjamin Griese:
Hello James,
thanks for replying giving us your opinion.
Sometimes I thought I was the only person who has the problem you're
talking of. I am in the same dilemma as you are, using SLES11 /w SP1
and have a not working solaris
Hello Ralf,
nice to know that someone from Novell is reading here, too.
Currently I have opened up a Service Request regarding this topic at
Novells Suport Center and pointed that out as a Feature Request but
also as problem I and other people have and are lookinf for a
workaround.
Too bad I am
While further searching the web I found this nice conclusion of how to
debug a Solaris 10 Native LDAP-Client or more general,
what is neccessary to know if you want to work with solaris native ldap client.
control?
-Dieter
-- Forwarded message --
From: Diego Lima li...@diegolima.org
Date: Fri, Oct 15, 2010 at 18:41
Subject: Re: Error 18: Solaris 10 Native LDAP-Client
To: Benjamin Griese der.dar...@gmail.com
Cc: openldap-technical@openldap.org
Hi Benjamin,
It looks like
Hello James,
thanks for replying giving us your opinion.
Sometimes I thought I was the only person who has the problem you're talking of.
I am in the same dilemma as you are, using SLES11 /w SP1 and have a
not working solaris nativ ldap client oder downgrading to SLES1 /wo
SP1 but using a rather
Benjamin Griese der.dar...@gmail.com writes:
Hello there,
I feel like spamming the list, but I now think its a more and more
OpenLDAP Server-related problem (for me its not a feature ;) ).
http://bacedifo.blogspot.com/2009/09/server-side-sort-with-openldap2418.html
I could reproduce the
Hello there,
a short update on my problem for the ppl who care. :)
A colleague of mine could reproduce the situation with the same
version of OpenLDAP 2.4.23 (from the OpenSUSE repo) and Solaris 10,
but there was no problem with an older version of OpenLDAP 2.4.12
(default in sles11 w/o sp1) and
Hi diego,
thanks for you advise. I created two new Overlays as you said and
tried to set the attribute-set that I googled from some other guys.
These are probably wrong. Finally, that solved the messages that
appeared in the slapd log, but didn't solve the problem on the solaris
hosts.
Too bad.
Update: the serverSort thing was a false-positive this morning, I
guess the client was still caching.
...
Oct 18 15:52:23 examplehost slapd[24946]: conn=9373 op=168 SEARCH
RESULT tag=101 err=18 nentries=0 text=serverSort control: No ordering
rule
Oct 18 15:52:23 examplehost slapd[24946]: conn=9373
Hello guys,
I got a problem while pulling information with the native ldap client
on my various solaris 10 machines from an openldap2-2.4.23-116.1
Maybe someone has any ideas, because I am on the end of mine.
I don't know what to do in the further steps to solve the problem.
the important
Hi Benjamin,
It looks like your LDAP client is asking the server to return ordered
results from looking at this line:
tag=101 err=18 nentries=0 text=serverSort control: No ordering rule
You may want to take a look at the server-side sorting overlay
(slapo-sssvlv) and/or the value sorting
13 matches
Mail list logo
