aboutsummaryrefslogtreecommitdiffstats
path: root/facebook/facebook-data.c
diff options
context:
space:
mode:
authordequis <dx@dxzone.com.ar>2017-10-16 22:11:42 -0300
committerdequis <dx@dxzone.com.ar>2017-10-16 22:11:42 -0300
commit24db488909604dd389b584c1f1ce43c549648dbe (patch)
treecd5bb0df1a81a8ed370540c800eb13bbb5051f3a /facebook/facebook-data.c
parent1e264442a48f33a5933c49a2c0332e426dcdb4a1 (diff)
downloadbitlbee-facebook-24db488909604dd389b584c1f1ce43c549648dbe.tar.gz
bitlbee-facebook-24db488909604dd389b584c1f1ce43c549648dbe.tar.bz2
bitlbee-facebook-24db488909604dd389b584c1f1ce43c549648dbe.tar.xz
Work chat login support (enable the "work" setting to use it)
This covers three autodetected login types: 1. Work account password Simple, very similar to normal account types 2. Linked personal account This is deprecated but still needed in some companies. Looks just like password auth to users. In rare cases there may be more than one work account linked to a personal account, in which case this will only use the first one. Usually they can be de-linked by assigning a password (see the official docs) 3. SSO This one is awkward. The password can be set to garbage and users will receive a PM with instructions to do an oauth-like login, but there's no explicit auth code screen, just a redirect to a fb-workchat-sso://, which probably results in an error. Users are expected to copy that url, hopefully from the address bar. Not very practical, but works! In all cases, the username is the work account email.
Diffstat (limited to 'facebook/facebook-data.c')
0 files changed, 0 insertions, 0 deletions