Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of sigzero@gmail.com designates
 209.85.161.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F070F29.1010006@ice-sa.com>
References: 
 <CALp+1QvCdYw=S+HAgYpadbKAP4hfKjx_RzCONSb8Zag=z00Byg@mail.gmail.com>
 <4F070F29.1010006@ice-sa.com>
From: sigzero <sigzero@gmail.com>
Date: Fri, 6 Jan 2012 10:14:46 -0500
Message-ID: 
 <CALp+1QtGinJtWDLicUOs6sw==KdPLJX5cq5aqGGuGYL=s8VqzA@mail.gmail.com>
Subject: Re: Tomcat and LDAP (handling password expiration)
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 6, 2012 at 10:11 AM, Andr=E9 Warnier <aw@ice-sa.com> wrote:
> sigzero wrote:
>>
>> The scenario is that Tomcat (6) is sitting on Windows and it talks to
>> an LDAP server sitting on Linux (RHEL). What is the best way to handle
>> the Tomcat LDAP account password expiring? I know that the password
>> needs to change on the LDAP and the Tomcat server.xml file needs to be
>> updated. I see no go way to automate that and the only workaround that
>> I see is to have the Tomcat LDAP account password not expire.
>>
> That is indeed the solution we had to get several of our customers to agr=
ee
> to.
> In general, that is a called a "service account" in sysadmin/netadmin
> parlance, and it generally means some paperwork..
>

Totally agree...security folks don't like that answer too much. I am
just doing some ground work to say "this is the way it is".

Thanks,

Bob

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org