=INFO REPORT==== 2008-05-14 14:43:59 ===
I(<0.1305.0>:ejabberd_c2s:418): (#Port<0.1517>) Failed legacy authentication for user@xxx.net/FSA_1.0_90-TM8SLI can create accounts using Gaim/Pidgin, but one client I am using wont work. What is legacy authentication?
% Authentication method. If you want to use internal user base, then use
% this line:
{auth_method, internal}.
% For LDAP authentication use these lines instead of above one:
%{auth_method, ldap}.
%{ldap_servers, ["localhost"]}. % List of LDAP servers
%{ldap_uidattr, "uid"}. % LDAP attribute that holds user ID
%{ldap_base, "dc=example,dc=com"}. % Search base of LDAP directory
%{ldap_rootdn, "dc=example,dc=com"}. % LDAP manager
%{ldap_password, "******"}. % Password to LDAP manager
Looking at the source code,
Looking at the source code, 'legacy' is used when client attempted to login using old plaintext authentication. When the SASL method described in XMPP protocol is used, then it says: 'Failed authentication for badlop@localhost'.
So you created an account, you can login to it using Pidgin, but you cannot login to it using another strange client?
legacy auth
So you created an account, you can login to it using Pidgin, but you cannot login to it using another strange client?
Yes, thats what is happening. The Strange client is an embedded device, which uses XMPP for status information.