We have implemented our authentication logic using JBoss' JAAS framework. It seems to work fine. But the one major thing is that we are unable to propagate the actual login/authentication failure from the authentication logic to the EJB client. e.g. user has been locked by system admin.
It always comes out as java.rmi.ServerException with the embedded EJBException and there is no sign of the message that was drummed up within the JAAS login module. Any solution for this one ? Or a workaround ?
We do have a need to inform the end user using the UI (EJB client) about the actual reason for failure and not always incorrect password for user.