[Bug 37376] New: Provide a pseudo-mechanism for vendor-specific SASL mechanisms

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=37376

           Summary: Provide a pseudo-mechanism for vendor-specific SASL
                    mechanisms
           Product: Telepathy
           Version: git master
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: gabble
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: will.thompson at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


I think Gabble (or Wocky, for that matter) should carry its own implementations
of X-GOOGLE-TOKEN and X-FACEBOOK-PLATFORM, and expose them when appropriate as
a pseudo-mechanism (X-TELEPATHY-OAUTH-TOKEN, say) which takes the token as
initial data.

This obviously doesn't mean that it shouldn't also offer the real mechanisms
too. But there's no reason why everyone who wants to do Facebook or Google
integration should have to re-implement these XMPP-specific mechanisms: they
should live in the XMPP component. And, if AIM or something switches to OAuth
authentication, Haze or whatever could implement this pseudo-mech and all would
be sweetness and light.

For a motivating example: GNOME Online Accounts provides methods to get an
OAuth or OAuth2 (as appropriate) token for an account. It would be nice if the
inevitable auth channel handler for GOA-based accounts didn't have to implement
these mechanisms, and it would also be nice to not have to bake them into GOA
(which would otherwise contain no XMPP-specific code), leaving Gabble as the
only remaining home :)

I guess we'd have to split OAuth1 and OAuth2.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.