Comment 3 for bug 1737212

additionally to applying the above patch it is required to add "--enable-webex-token" to DEB_CONFIGURE_EXTRA_FLAGS before build.

I have tested the build on top of artful universe pidgin-src 2.12.0-1ubuntu2_amd64 and the patch works for me in regards that I can use my corporate SingleSignOn to connect to Cisco WebEx XMPP.

additional infos from original patch related to be able to use the provided SSO Method:

From a Cisco Jabber Client install, look for a SSOAuthInfoStore.xml file. In my example on my Windows Cisco Jabber install I used C:\Users\<myusername>\AppData\Roaming\Cisco\Unified Communications\Jabber\CSF\Config\SSOAuthInfoStore.xml

This should contain a URL on loginp.webexconnect.com (or the like) specifying a SSO login url for your corporate SSO. It should look similar to: https://loginp.webexconnect.com/cas/FederatedSSO?org=<your_corp_domain>&type=connect2

Once you open that URL with a browser and complete whatever authentication workflow is needed, you will get an XML stanza back called FederatedSSO. If you already have an SSO cookie set in your Browser, because you already authenticated your Corp SSO for another service, you'll just get an XML response with the required token data.

In the returned stanza, you will need to copy the <jabbertoken> element, and use that as your password. Returned <screenname> should match your user and domain elements in your account configuration in Pidgin, regardless of your usual corporate username and domain name. Finally, you will want to use the server in the <xmppjabbercluster> element as your target server to connect to (note there is also a <jabbercluster> element, do not use that). Port 5222 should work for Cisco Jabber via WebEx.

Note that the token will expire (the XML will tell you when) and after that when you restart pidgin you'll need to get a new token and update your config with the new token as password.