On Saturday 19 November 2016 12:49:00 Pali Rohár wrote: > Hello! > > New feature in Kopete 1.11 (part of KDE Applications 16.12) is > support for X-OAUTH2 SASL authentication in jabber protocol. It is > alternative to clear-text password based authentication. > > Currently it is possible to do X-OAUTH2 authentication either via > Access Token or via Refresh Token. In second case it is needed to > provide also Client ID, Client Secret Key and Request URL (for HTTP > request which will generate Access Token from provided Refresh > Token). > > X-OAUTH2 authentication and its tokens can be configured in > Connection tab in Edit Account settings dialog. > > Note that it is not possible to do X-OAUTH2 authentication via > Application Code. If such feature is needed and authentication via > Refresh Token or Access Token is not enough then let me know and we > can discuss about it. > > X-OAUTH2 was tested also with Google's XMPP server and it is working > fine. So it can be useful for google accounts with disabled (or not > available) clear-text password authentication. Or for people who do > not want to send clear-text password in TLS tunnel to google servers > (as google does not support SCRAM)...
Just to add information, Kopete in 16.12 branch has fixed problems with OTR encryption plugin, namely show correct icon of encryption status (enabled/disabled) and fixed crash after generating encryption key. -- Pali Rohár pali.ro...@gmail.com
signature.asc
Description: This is a digitally signed message part.
