#1141 closed defect (worksforme)

Purple builds suggest using oauth for jabber, but it's not implemented

Reported by: dx Owned by: wilmer
Priority: normal Milestone:
Component: Purple Version: 3.2.1
Keywords: Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:


The jabber oauth implementation only exists in the native bitlbee jabber module. When using libpurple, the user still gets instructions to do "account jabber set oauth on", only to find that the setting doesn't exist.

Attachments (0)

Change History (3)

comment:1 Changed at 2014-07-19T00:43:46Z by dx

Resolution: worksforme
Status: newclosed

I originally made this bug report based on what a user on #bitlbee said, but now i tested it and this doesn't happen. Whatever.

comment:2 Changed at 2015-04-24T18:11:40Z by dale@…

I just ran into this on OSX.

brew install bitlbee --with-libotr --with-pidgin

oauth does not show up on the acc jabber set list.

comment:3 Changed at 2015-04-24T19:49:55Z by dx

This ticket is about bitlbee show a message suggesting you to use oauth. We can't fix the fact that libpurple doesn't have oauth.

You can, however, rebuild with in a way that ensures that "--jabber=1" is passed to the ./configure command (and that the configure output shows jabber in the list of enabled protocols). That will get you the native jabber instead of the libpurple one.

Modify Ticket

as closed The owner will remain wilmer.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.