call, and This hits the server as expected, but when the comparison between the sent password and the database password occurs, there is a mismatch as the password in the database in encrypted. Is there a way to:
1) create a custom login command that can encrypt the password before the comparison is made;
2) A way to create a filter that will intercept the channelset.login() call, so that the password can be removed from the call and replaced with the encrypted version of it?
I am using java/Spring/Spring-security/BlazeDS and CAS as the server side technologies.