tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 22236] - JNDI Realm authentication to Novell eDirectory via LDAP
Date Tue, 12 Aug 2003 21:45:49 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22236>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22236

JNDI Realm authentication to Novell eDirectory via LDAP

ladams@ccc.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ladams@ccc.edu
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |



------- Additional Comments From ladams@ccc.edu  2003-08-12 21:45 -------
I've been running into the same problem.  Coincidentally, also using Novell
eDirectory.  Perhaps Novell is unique in returning roles with null attributes?

I have a user, it belonged to a group called intranet.  I was able to
authenticate an application using this role.  Then my Novell admin added the
user to a new group, and I started getting the NPE.  Turns out the second group
I was added to returns null attributes.

I got around the NPE a while back by adding that null check, but I think the
right thing to do is to modify the addAttributeValues method to return the
original "values" argument that was passed to the method.  In my case, the null
values on the second role returned in my SearchResults were causing the whole
list to be nullified, and I couldn't authenticate even though the intranet role
was found.

Mime
View raw message