[Bug 32125] Should support auth using captcha

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 30 13:49:16 CET 2012


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

--- Comment #8 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2012-01-30 04:49:16 PST ---
        <p>Typical values: "", Cancelled, AuthenticationFailed,
NotAvailable</p>

I realise I may have contradicted myself. Does Not_Supported from the
cancellation enum map to the error NotAvailable, NotImplemented or a new
CaptchaNotSupported?

I think NotAvailable should be ruled out, because that's what we'd get (as
noted in Comment #6) if the server thinks we took too long; a new
CaptchaNotSupported (meaning "either we don't have a UI to present captchas, or
we do but it wasn't able to answer any of the captchas we were given") is
probably the best option.

        <p>In particular, an ordinary authentication failure (as would
          be produced for an incorrect answer) SHOULD be represented by
          <tp:error-ref>AuthenticationFailed</tp:error-ref>,
          cancellation by the user's request SHOULD be represented
          by <tp:error-ref>Cancelled</tp:error-ref>, and
          cancellation by a local process due to inconsistent or invalid
          challenges from the server SHOULD be represented by
          <tp:error-ref>ServiceConfused</tp:error-ref>.</p>

This should mention the Not_Supported case, whatever that ends up being.

If we want ServiceConfused to be possible here, then we should have a
Service_Confused cancellation reason in the enum, so the UI can tell us that it
thinks the server is giving it gibberish.

-- 
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.



More information about the telepathy-bugs mailing list