Unless the docs just haven't been updated yet, it looks like it still has the same JNDI Realm support that it had before. i.e. it uses an admin DN to log into the LDAP server and then queries the userPassword attribute for the user and compares the passwords. I'm hoping that the method where it does an LDAP bind as the user himself will be implemented. I know someone had a patch that does this. The question is whether or not that patch will be in 4.1 or not.
Jon ----- Original Message ----- From: "Rick Fincher" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]>; "Jonathan Eric Miller" <[EMAIL PROTECTED]> Sent: Monday, May 06, 2002 1:16 PM Subject: Re: [ANNOUCEMENT] Apache Tomcat 4.1.0 Alpha > Hi Jon, > > I have not used it, so I can't say how well it works but the 4.1 server.xml > and example webapps have examples showing how use JNDI for that. The admin > webapp (kind of confusing terminology, manager now refers mostly to > persistence management and the admin webapp is the administration interface) > will use it to administer users, roles, etc. > > Rick > > > Does anyone know if this release contains the new JNDI Realm code that > > allows you to authenticate users using LDAP binds instead of querying the > > directory for the password and comparing? > > > > Jon > > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
