Message from discussion
Active Directory problem
MIME-Version: 1.0
Received: by 10.100.111.15 with SMTP id j15mr269901anc.11.1233878993423; Thu,
05 Feb 2009 16:09:53 -0800 (PST)
Date: Thu, 5 Feb 2009 16:09:53 -0800 (PST)
In-Reply-To: <498B740B.1010501@intient.com>
X-IP: 60.240.142.21
References: <0b78c192-5ee2-49d5-9837-ed458275fed0@o40g2000prn.googlegroups.com>
<498B740B.1010501@intient.com>
User-Agent: G2/1.0
X-HTTP-Via: 1.1 SMSTSISA01
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2; .NET CLR
1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30),gzip(gfe),gzip(gfe)
Message-ID: <a4dc2762-f783-405f-8be1-93ceeac17bf1@w1g2000prm.googlegroups.com>
Subject: Re: Active Directory problem
From: Michael <MichaelBli...@hotmail.com>
To: ESOE Users <esoe-users@googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hello Bradley,
Thanks for your quick reply (I went off for a coffee). Yes, nslookup
does resolve correctly, as shown below. I have updated adminUser-1 to
"tsadmin,dc=3Dtsdev,dc=3Dinside" or "tsadmin,cn=3Dusers,dc=3Dtsdev,dc=3Dins=
ide"
without luck.
I also noticed the following in esoe-authn.log - is the lack of
something at the end a concern?
2009-02-06 09:23:05,765 ERROR esoe.authn - Failed to authenticate
principal tsadmin to underlying authentication mechanism identified by
external ESOE ID of:
Results of nslookup:
C:\Documents and Settings\mblight>nslookup smstsdc01
Server: smstsdc01.tsdev.inside
Address: 192.168.20.1
Name: smstsdc01.TSDEV.Inside
Address: 192.168.20.1
On Feb 6, 10:19=A0am, Bradley Beddoes <bedd...@intient.com> wrote:
> Hi Michael,
>
> Michael wrote:
> > Hi All,
>
> > I have got past a few problems with installation, and have finally got
> > to the login page, but continually come up with a login failure. =A0I
> > have tested my LDAP connection and credentials using an LDAP browser
> > and they work fine, but I am no expert here.
>
> > I have tried a few options by stopping Tomcat, changing the "## LDAP
> > Server 1 Connection" section of esoe.config and restarting. =A0Is this
> > going to pick up my changes? =A0The current details are:
>
> > ldapURL-1=3Dldap://smstsdc01
>
> This needs to be the server DNS entry does 'nslookup smstsdc01' resolve
> in DNS for you?. If not you'll need something like smstsdc01.company.com
>
> > ldapServer-1=3Dsmstsdc01
> > ldapServerPort-1=3D389
> > baseDN-1=3DDC=3DTSDEV,DC=3DInside
> > identifier-1=3DsAMAccountName
> > recursive-1=3Dtrue
> > disableSSL-1=3Dtrue
> > adminUser-1=3Dtsdev\tsadmin
>
> This needs to be a DN so something like
> sAMAccountName=3Dtsadmin,dc=3Dtsdev,dc=3Dinside - please adjust according=
ly
> for your environment.
>
> > adminPassword-1=3Dneveryoumind
>
> > I have tried the "ldapURL-1" with/without port, and "baseDN-1" with/
> > without "CN=3DUsers". =A0The default for "identifier-1" in this section=
is
> > "uid", but the LDAP browser shows no such property. =A0I have tried
> > replacing it with "sAMAccountName", which the LDAP browser shows as
> > being the account name, but it doesn't work.
>
> sAMAccountName for AD is the best option, you can add the cn=3Dusers to
> baseDN if you like but get it working without this first would be my
> recommendation.
>
>
>
>
>
>
>
> > During installation I did the following that was slightly different
> > from the instructions:
> > - Edited generate_db-mysql to comment out the constraints as they
> > caused problems with MySQL.
> > - Ignored the installation step of "Extract spep-shared.tar.gz to your
> > $TOMCAT/shared/lib directory of the tomcat instance which will run
> > esoemanager" as the file did not exist.
> > - I was confused by "Your database itself is already configured,
> > undertake the following for your environment." as no database had been
> > created, and the in the next step it was to be used. =A0In MySql I
> > manually created the esoe database, after setting the engine to InnoDB
> > (to fix something).
>
> > I am using Windows 2003, Tomcat 5.5, MySql 5.1.30, JRE 6, and the
> > "current" build of OSOE (which I assume is 0.5.2 or thereabouts).
>
> =A0From memory that is the latest binary build versioning, things have
> progressed significantly in SVN head however.
>
>
>
> > If anybody can help with the Active Directory integration I would be
> > very grateful.
>
> Hopefully the above is of assistance.
>
> --
> Bradley Beddoes
> Lead Software Architect
>
> Intienthttp://www.intient.com
>
> Telephone
> Australia: (07) 3102 4560
> United States: (424) 785-0434- Hide quoted text -
>