[Bug 291869] New: Auth handler should also be an observer (aka non-interractive approver)
George Kiagiadakis
kiagiadakis.george at gmail.com
Wed Jan 18 14:57:21 UTC 2012
https://bugs.kde.org/show_bug.cgi?id=291869
Summary: Auth handler should also be an observer (aka
non-interractive approver)
Product: telepathy
Version: git-latest
Platform: Unlisted Binaries
OS/Version: Linux
Status: NEW
Severity: normal
Priority: NOR
Component: auth-handler
AssignedTo: kde-telepathy at kde.org
ReportedBy: kiagiadakis.george at gmail.com
It turns out that empathy-auth-client is also an observer as well as a handler.
This causes trouble when empathy is co-installed with kde-telepathy.
The empathy auth process works like this:
* empathy-auth-client is launched as an observer
* while being an observer, it checks if the account is a GOA account or if the
password for this account is otherwise saved in gnome-keyring.
* if either of this is true, it claims the channel and becomes a handler for
it, providing the authentication details to the CM.
* if none is true, it lets the channel be dispatched normally
The problem of course is that when MC looks for a handler, because
empathy-auth-client is already running as an observer, MC gives it a high
preference and picks it up again as a handler.
In ktp we should do something similar. The concept of having an observer claim
a channel is called a non-interractive approver. The idea is that it is called
silently before any other approvers and it can claim the channel if it believes
it should do so. This way we can ensure that our auth handler is the one that
is always picked for accounts that have been configured through kde-telepathy.
More info: http://telepathy.freedesktop.org/spec/Client_Observer.html
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the KDE-Telepathy
mailing list