Because my last post was hung up from the original thread.
===
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.
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 bas
Am Dienstag 02 November 2010, 18:03:56 schrieb Ralf Haferkamp:
> Am Dienstag 02 November 2010, 16:57:38 schrieb Benjamin Griese:
[..]
>
> Something like this should work:
>
> access to dn.base="" attrs=supportedControl
> val/objectIdentifierMatch=1.2.840.113556.1.4.473
> by * none
> access to d
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,shadowLastChan
Hello Ralf,
yes you're right that's the right SR, and yes it's about dynamic
loading of modules.
I pointed Austin right to you and this thread, just for better communication.
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
Am Dienstag 02 November 2010, 16:57:38 schrieb Benjamin Griese:
> 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 pr
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
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 sol
Benjamin,
We have a similar problem where upgrading to OpenLDAP 2.4.20 on SLES 11
causes Outlook 2003 clients to not work right with an ldap address book on
OpenLDAP. Microsoft has this documented here:
http://support.microsoft.com/kb/36
In this case, the reg hack works.
I can't say whethe
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 o
Dieter
>
> -- Forwarded message --
> From: Diego Lima
> Date: Fri, Oct 15, 2010 at 18:41
> Subject: Re: Error 18: Solaris 10 Native LDAP-Client
> To: Benjamin Griese
> Cc: openldap-technical@openldap.org
>
>
> Hi Benjamin,
>
> It looks like your
Just for completion, this was the first reply to my problem who
pointed me into the direction of sssvlv and valsort.
-- Forwarded message --
From: Diego Lima
Date: Fri, Oct 15, 2010 at 18:41
Subject: Re: Error 18: Solaris 10 Native LDAP-Client
To: Benjamin Griese
Cc: openldap
Benjamin Griese writes:
> Correction:
> -w or -w - instead of -W
>
> On Thu, Oct 28, 2010 at 15:02, Benjamin Griese wrote:
>> Hello Günther,
>>
>> sorry for my late reply, I hate sun cluster panics after patching
>> those beasts. :(
>>
>> Here is the content of solaris_profile:
[...]
>> If I t
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.
http://wiki.genunix.org/wiki/index.php/Native_LDAP_Product_Support_Document#What_are_the_req
Correction:
-w or -w - instead of -W
On Thu, Oct 28, 2010 at 15:02, Benjamin Griese wrote:
> Hello Günther,
>
> sorry for my late reply, I hate sun cluster panics after patching
> those beasts. :(
>
> Here is the content of solaris_profile:
>
> dn: cn=solaris_profile,ou=profile,dc=example,dc=de
Benjamin Griese 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 problem an 2
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 problem an 2.4.20, but havn't been able to setup
an
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
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
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. :/
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 overl
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 informati
22 matches
Mail list logo
