SLUG Mailing List Archives
Re: [SLUG] Invalid credentials error code 49
- To: slug@xxxxxxxxxxx
- Subject: Re: [SLUG] Invalid credentials error code 49
- From: "Gonzalo Servat" <gservat@xxxxxxxxx>
- Date: Thu, 20 Apr 2006 00:36:57 -0300
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GdKqtW/ALWB41jjmvqfYNiOn8BoIE1yZn5KVzdAIE452dRVQv1JHBBMB+9hAat0VTgAkzGaBj7zxXvf7jYnnugkk9OxOL8Bp9WvvSm8RABS7njjfUsvH9W5DWuvsg35U3ZtYlbBIaklqS0+qXdaBs26b2RVpEmYncaKtZ7YAUvc=
On 4/20/06, O Plameras <oscarp@xxxxxxxxxxx> wrote:
> Jamie Wilkinson wrote:
> > I made my judgement based on the facts presented by Selim. The appearance
> > of "dc=example,dc=org" in the DN has no bearing on DNS or network. It is
> > merely an identifier within the LDAP directory itself.
> > I will not "wait for outcome" when I can see that your misdirections will
> > only lead them to waste their time.
Jamie is right, the fact that Selim is using dc=example,dc=org is not
the cause of the problem. As you can imagine, if there was any
relation between the base DN and a real internet domain name, then the
slapd.conf wouldn't include dc=example,dc=org as the default, they
would make it dc=CHANGEME,dc=NOW and a big warning around it, don't
Selim: just for kicks, try generating a new password like:
slappasswd -s foo
and, obviously, paste it in the rootpw line, restart slapd and try to
bind again. Any luck?