powered by Jive Software

Adium 1.0.5 failing to connec to Openfire

Hi all,

I recently deployed Openfire on a server of ours. Our users are pulled through an LDAP database; when users connect with Pidgin or Trillian, they can log in fine. However, Adium 1.0.5 does not allow a connection, and I’'m wondering if there is anything peculiar about Adium that needs to be addressed.

The connection from Adium just hangs - there is no indication that anything is being done.

Please let me know if I can provide more information. Thanks.

If you could try the beta of Adium 1.1 available at http://beta.adiumx.com it a) has a number of xmpp improvements, and b) has debug logging enabled, which you can find in the Adium menu. If it still doesn’'t connect, feel free to drop by the Adium irc channel (#adium on irc.freenode.net) or file a bug report at http://trac.adiumx.com

Adium uses the same library as Pidgin, so it will work the same way. I would double check all your configuration information in Adium to make sure its correct.

Going to have to disagree with you there. libpurple is not the same as pidgin itself. while the library may be the same, the plugin that adium uses is quite different then pidgin. For example you can change your password in Pidgin but you can’'t in Adium, Pidgin properly registers itself whereas Adium does not (http://trac.adiumx.com/ticket/7049).

However your inability to connect shouldn’‘t be caused by that. Make sure old style SSL isn’'t enabled.

Thank you all for your input - I will look into these options and report back what I find.

Okay, progress! The users with the Adium 1.1 beta can now connect to Openfire - the console shows them as logged in and authenticated - but their rosters aren’‘t autopopulating (even though that LDAP group is set to share) - also, they aren’'t appearing on our buddy lists, so the lack of autopopulation goes both ways …

I appreciate any further advice you might have.

yvovandoorn wrote:

Going to have to disagree with you there. libpurple is not the same as pidgin itself. while the library may be the same, the plugin that adium uses is quite different then pidgin. For example you can change your password in Pidgin but you can’'t in Adium,

This is due to Adium 1.1 not implementing libpurple’'s fields request. This has been implemented for 1.2 during my Summer of Code project.

Pidgin properly registers itself whereas Adium does not (http://trac.adiumx.com/ticket/7049).

This is probably due to Adium using a beta version of libpurple. This is a non-issue in 1.2, too, since the registration has been rewritten.