Now I'm making the openldap and Kerberos working together, I have a question
about the password the ldap used. The configuration file
/usr/local/etc/openldap/slapd.conf has these lines:
# rootpwsecret
rootpw {SSHA}n+R5iqJRHTiaosqPJVx03NF+bIStW6pQ
while the second line is g
On 4/3/07, Rocky Zhou <[EMAIL PROTECTED]> wrote:
Now I'm making the openldap and Kerberos working together, I have a question
about the password the ldap used. The configuration file
/usr/local/etc/openldap/slapd.conf has these lines:
# rootpwsecret
rootpw {SSHA}n+R5iqJRH
When running 'make test', if any of the tests fail, will the testing
continue or will it stop all further tests?
I'm wondering if I should be parsing the test output and reviewing it to
ensure proper builds.
Thanks,
--
Joshua M. Miller - RHCE,VCP
OK i will test our Red Hat gold support. it's the fisrt time !
and if they cannot do anything i will upgrade openldap.
Thomas
> Message du 02/04/07 à 15h50
> De : "Aaron Richton"
> A : "[EMAIL PROTECTED]"
> Copie à : openldap-software@openldap.org
> Objet : Re: err=52
>
> On Mon, 2 Apr 200
--On Tuesday, April 03, 2007 7:39 AM -0700 Josh Miller
<[EMAIL PROTECTED]> wrote:
When running 'make test', if any of the tests fail, will the testing
continue or will it stop all further tests?
I'm wondering if I should be parsing the test output and reviewing it to
ensure proper builds.
If
This is a followup to a thread from a couple of months ago. The issue is
interaction between ppolicy and syncrepl overlays. The message I want to
start at is:
http://www.openldap.org/lists/openldap-software/200701/msg00131.html
which didn't get a direct reply. Here's a quote of the relevant conte
Craig Squires wrote:
This is a followup to a thread from a couple of months ago. The issue is
interaction between ppolicy and syncrepl overlays. The message I want to
start at is:
There is no "syncrepl overlay". (Possibly there should be, but that work
got stalled.) The syncrepl consumer is in
Thanks, Howard; I think I'm beginning to understand this.
So, the AUTHENTICATION piece is done by SASL using digest_md5, an
'external' connection to TLS, etc. But the AUTHORIZATION piece is
handled by the rules defined in the access control policy section of
slapd.conf, right?
Thanks
tl
-O
[EMAIL PROTECTED] wrote:
Thanks, Howard; I think I'm beginning to understand this.
So, the AUTHENTICATION piece is done by SASL using digest_md5, an
'external' connection to TLS, etc. But the AUTHORIZATION piece is
handled by the rules defined in the access control policy section of
slapd.conf,