I am not sure whether it has to be reported to as a feature request or bug. Please suggest.
I have been using pidgin/sipe for connecting to Skype for Business for long time. It stopped working a couple of days before.
As suggested in this page "https://sourceforge.net/p/sipe/discussion/688534/thread/497bf3fa72/, I have tried to setup User Agent but it did not help.
I am trying to login to my company's (hcl.com) Skype for business account using my client's laptop (staples.com).
Configuration:
Windows 7
Pidgin: 2.13.0
* SIPE: 1.24.0
Could you help?
Thanks in advance!
Based on the provided information this is covered in the FAQ. As unsafe debug logging wasn't enable, as requested by FAQ, I'm unable to tell if the provided solution was applied correctly:
~~~~~
:::txt
(22:18:14) sipe: sipe_http_transport_connected: login.microsoftonline.com:443(0254C168)
(22:18:14) sipe: MESSAGE >>>>>>>>>> HTTP(0254C168)
(22:18:14) sipe: transport_input_common: new buffer length 4096
(22:18:14) sipe: MESSAGE <<<<<<<<<< HTTP(0254C168)
(22:18:14) sipe: sipe_http_request_response_callback: cookie: fpc=ApUkotS9KQdOtYLGImhwL9XG1BG2AQAAAGZ5adQOAAAA; HttpOnly
...
(22:18:14) sipe: sipe_svc_https_response: code 200
(22:18:14) connection: Connection error on 04D0E148 (reason: 2 description: Web ticket request to https://webdir0F.online.lync.com:443/CertProv/CertProvisioningService.svc failed
(AADSTS53003: Blocked by conditional access.))
(22:18:15) account: Disconnecting account rajamani.muniappan@hcl.com, (024A49B0)
~~~~
Other possibilities are that Microsoft has changed what user agent values are accepted or your IT has disabled access for mobile clients.
As you use Windows you of course have the fallback option of using the official SfB client too.
Closing as NOTABUG
Last edit: Stefan Becker 2019-05-12