Yeah it looks like the fix to make the encoding only on the DN instead
of the whole string was applied after 4.1.30 was tagged. It will have
to be in a future release.
>>> [EMAIL PROTECTED] 3/25/04 5:56:16 PM >>>
Pascal,
What version of Tomcsat are you using? In response to a defect, I
added
I ran into the same problem after upgrading from Tomcat 4.1.29 to
4.1.30. The problem was with the parens in the roleSearch attribute of
my JNDIRealm. It does look like the parenthesis are being encoded (the
\28 and \29) when they shouldn't be. For now, though, I got it working
by removing t
I'm using Tomcat 5.0.18 (going to upgrade soon, but I'm using this
version to do documentation at the moment), and OpenLDAP 2.1.22.
I configured OpenLDAP to log everything, and here's the error (as you
suspected):
1. Tomcat authenticates the user, but cannot find the role he belongs
to. Below
Pascal,
What version of Tomcsat are you using? In response to a defect, I
added a feature to JNDIRealm a while back, that applied a "filter" to
certain JNDI realms to encode characters such as " and (
Later we learned that I should have focused that filtering a little
more on a specific string
Hello, all !
I've got a really strange problem that is probably caused by my
eyesight. I followed the JNDI Real HowTo on the Jakarta site, and I
setup the necessary LDIF file and put the necessary entries inside
server.xml. After struggling with various typo errors and configuration
mistakes (
