Changes for Kopete in KDE Applications 16.12

Pali Rohár <[email protected]>
Newsgroups gmane.comp.kde.promotion,gmane.comp.kde.devel.kopete
Message-ID <201611191249.00363@pali>
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)...

-- 
Pali Rohár
[email protected]
signature.asc (application/pgp-signature, 198 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAlgwPCwACgkQi/DJPQPkQ1Je5QCbBzE6yYtgPKAOLObYs3/Oelr9
pWcAoKsIXQvwJUCBw16M0D7hEKf2k6m6
=AyQH
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.