So I'm having a little trouble understanding why I can't filter an
attribute in one DN, but I can filter an attribute in another DN:
Here's the first search, to show the dn and attribute (o:
example.com) actually exists:
# ldapsearch -x -D "cn=Manager,dc=example,dc=ca" -W -b
'ou=hosting,o
hello its been a bit for me using openldap.. so getting back into it now
with a new project.
quick synopsis.. an oracle database holds a truckload of data that is in
a fairly large state of flux.. I currently pull nightly feeds from this
database to maintain the data in my openldap systems. This
On 27-Jun-06, at 2:01 PM, Kurt D. Zeilenga wrote:
At 09:38 AM 6/27/2006, Jason Lixfeld wrote:
I think I'm somewhat versed in the basics of OpenLDAP, but the
concept of access policies eludes me because they are far beyond my
current level of comprehension. That being said, I'm doing some
tria
At 10:35 AM 6/27/2006, Jason Lixfeld wrote:
>Ok, I think I'm making some headway, but I'm still a little confused.
>
>I didn't realize that by putting in an access entry to permit
>specific stuff, you have to put other entries in for everything else
>or else it's an implicit deny. That being s
At 09:38 AM 6/27/2006, Jason Lixfeld wrote:
>I think I'm somewhat versed in the basics of OpenLDAP, but the
>concept of access policies eludes me because they are far beyond my
>current level of comprehension. That being said, I'm doing some
>trial by fire to try to make sense of how they wo
Ok, I think I'm making some headway, but I'm still a little confused.
I didn't realize that by putting in an access entry to permit
specific stuff, you have to put other entries in for everything else
or else it's an implicit deny. That being said, I modified my
slapd.conf as follows:
ac
I think I'm somewhat versed in the basics of OpenLDAP, but the
concept of access policies eludes me because they are far beyond my
current level of comprehension. That being said, I'm doing some
trial by fire to try to make sense of how they work and hopefully
will then be able to relate s
Sandeep-
I had a similar problem when I first enabled password policy and I traced
it down to the fact that existing accounts did not have one of the
operational attributes and so openldap considered the account's password
to be expired. I can try to figure out which attribute it was if you
w
At 02:35 AM 6/26/2006, TJ wrote:
>I'm having difficulty processing the response from the password policy control
>returned by slapd
>
>here is an extract of the log:
>
>send_ldap_result: conn=45 op=4 p=3
>send_ldap_result: err=19 matched="" text="Password is in history of old
>passwords"
>send_ld
I am able to rectify this issue by creating the accout again.
This problem happens only to the accouts which exists before adding the
ppolicy directive.
And it is not happening to the account which I created later.
As a workaroud I deleted all the accounts and created it again.
I got this poin
On Monday 26 June 2006 10:30, Magnus Morén wrote:
>
> Questions:
>
> 1) Anyone knows why it is that RedHat sticks to and old version of
> OpenLDAP if there are known bugs in it. They usually do a great job with
> most of their other software.
It seems the RH has OpenLDAP in the distribution main
11 matches
Mail list logo
