[
https://jira.jboss.org/jira/browse/EJBTHREE-794?page=com.atlassian.jira.p...
]
Bjørn Ola Smievoll commented on EJBTHREE-794:
---------------------------------------------
This isn't a EJB 3.0 specific issue, any remote client doing login is prone to this as
it's origins lay in the JAAS-ldap backend, so it should really be moved to JBAS or
SECURITY where it might get some attention.
If no workaround exists I'll raise a support case through support.
NotSerializableException from LdapLoginModule/AD
------------------------------------------------
Key: EJBTHREE-794
URL:
https://jira.jboss.org/jira/browse/EJBTHREE-794
Project: EJB 3.0
Issue Type: Bug
Environment: jboss 4.0.5.GA/JEMS install, Win2000, ActiveDirectory
Reporter: Darren Hartford
"java.io.NotSerializableException: com.sun.jndi.ldap.LdapCtx"
When incorrect credentials are passed from the client, the server swallows with
NotSerializableException and the client does not get correct feedback.
Test environment was login-config.xml with org.jboss.security.auth.spi.LdapLoginModule
talking to an ActiveDirectory server. Note that when correct credentials are passed,
everything works fine.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira