Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <3FAE5F19.7070303@joedog.org>
Date: Sun, 09 Nov 2003 10:36:57 -0500
From: Tim Funk <funkman@joedog.org>
Organization: Human being
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.4) Gecko/20030624
MIME-Version: 1.0
To: Tomcat Users List <tomcat-user@jakarta.apache.org>
Subject: Re: LDAP Configuration And Passwords
References: <83DD1986DE996945886399CF2A3B5F7C06F32E@vsti01.vsti.local>
In-Reply-To: <83DD1986DE996945886399CF2A3B5F7C06F32E@vsti01.vsti.local>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

You can extend JNDIRealm on your own to create your own authentication.

The ideal solution is the read protect server.xml so only the appropraite 
parties are allowed to read it. Anything else is "insecure." (Except having 
someone type in a password at start up which tomcat doesn't have that 
functonality)

-Tim

Edwin K. Brown wrote:
> Hello,
> I have set up Tomcat in the standalone mode to do user authorization by using LDAP.
> 
> We don't allow anonymous browsing of the LDAP tree, so the connectionUser and connectionPassword attributes have to be used in the JNDIRealm configuration.
> 
> However, for obvious reasons, having the user name and password in the server.xml file is not a good idea.
> 
> Is there any other way to address this problem?
> 
> Thank you.
> 


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