#1136 closed defect (notabug)

Cannot set authentication tls for sipe account (pidgin works fine though)

Reported by: lyncuser Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 3.2.1
Keywords: sipe authentication scheme ntlm tls Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:

Description (last modified by dx)

In pidgin to connect to the lync server of my company I need to adjust the useragent to CCAPI/4.0.7577.0 OC/4.0.7577.0 and the authentication scheme to tls-dsk. This works with pidgin.

I try to do the same with bitlbee however I cannot change the authentication scheme from ntlm to tls, so the connection always fails with,

<user> acc 1 on
<root> sipe - Logging in: Connecting
<root> sipe - Login error: Incompatible authentication scheme chosen
<root> sipe - Logging in: Signing off..
<user> acc 1 set
<root> authentication = `ntlm'
<root> auto_connect = `true'
<root> auto_reconnect = `true'
<root> away is empty
<root> display_name is empty
<root> email = `'
<root> email_login = `'
<root> email_password = `'
<root> email_url = `'
<root> groupchat_user = `'
<root> nick_format is empty
<root> nick_source = `handle'
<root> password = `********' (hidden)
<root> server = `'
<root> sso = `true'
<root> status is empty
<root> tag = `sipe'
<root> transport = `auto'
<root> useragent = `CCAPI/4.0.7577.0 OC/4.0.7577.0'
<root> username = `******************************************'

Here I try to switch to 'tls' but the bitlbee server on localhost answers always with 'ntlm'

<user> acc 1 set authentication = 'tls'
<root> authentication = `ntlm'
$ dpkg -l | egrep "bitlbee|sipe"
ii  bitlbee-common                             3.2.1+otr4+20140214+devel+1011-1                    An IRC to other chat networks gateway (common files/docs)
ii  pidgin-sipe                                1.13.1-2                                            Pidgin protocol plugin to connect to MS Office Communicator

Attachments (0)

Change History (6)

comment:1 Changed at 2014-03-01T03:27:42Z by dx

Description: modified (diff)

(added code blocks to description)

Errrr... how are we supposed to test this weird protocol?

comment:2 Changed at 2014-03-01T03:36:16Z by dx

Priority: majornormal

comment:3 Changed at 2014-03-02T08:14:02Z by anonymous

Is the standard protocol for the most recent version of lync. you can test against any recent lync server.

comment:4 Changed at 2014-08-13T11:11:20Z by dx

Resolution: notabug
Status: newclosed

Okay flexo pointed out on irc that you should do this instead

acc 1 set authentication tls-dsk

The "=" part in the command was causing it to be ignored, and the correct name is tls-dsk

He also updated the wiki page to mention this and a few other details like the new user agent:

(this page was named bitlbee-sipe recently, i renamed it)

BTW, I still don't know where to get a lync server (other than installing the trial package from microsoft's website), but i'll just redirect issues like this to flexo the next time.

comment:5 Changed at 2015-02-15T19:32:34Z by anonymous

A lync server is not required, use a trial version from lync online? Sign up at

comment:6 Changed at 2015-02-15T20:38:36Z by dx

Awesome. Thanks!

Modify Ticket

as closed The ticket will remain with no owner.
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.