- Timestamp:
- 2011-12-26T10:50:34Z (13 years ago)
- Branches:
- master
- Children:
- 5f40da7
- Parents:
- 9a1c14d
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
protocols/jabber/sasl.c
r9a1c14d r644b808 105 105 } 106 106 107 if( !sup_plain && !sup_digest && !sup_gtalk && !sup_fb && !sup_ms ) 108 { 109 imcb_error( ic, "BitlBee does not support any of the offered SASL " 110 "authentication schemes:%s", mechs->str ); 107 if( !sup_plain && !sup_digest ) 108 { 109 if( !sup_gtalk && !sup_fb && !sup_ms ) 110 imcb_error( ic, "This server requires OAuth " 111 "(supported schemes:%s)", mechs->str ); 112 else 113 imcb_error( ic, "BitlBee does not support any of the offered SASL " 114 "authentication schemes:%s", mechs->str ); 111 115 imc_logout( ic, FALSE ); 112 116 g_string_free( mechs, TRUE ); … … 294 298 if( jd->flags & JFLAG_SASL_FB ) 295 299 { 296 /* Facebook proprietary authentication. Not as useful as it seemed, but 297 the code's written now, may as well keep it.. 298 299 Mechanism is described on http://developers.facebook.com/docs/chat/ 300 and in their Python module. It's all mostly useless because the tokens 301 expire after 24h. */ 300 /* New-style Facebook OAauth2 support. Instead of sending a refresh 301 token, they just send an access token that should never expire. */ 302 302 GSList *p_in = NULL, *p_out = NULL; 303 303 char time[33];
Note: See TracChangeset
for help on using the changeset viewer.