Open Bug 2046212 Opened 5 months ago Updated 5 months ago

Allow aborting a verifyLogon call

Categories

(MailNews Core :: Networking, task)

Thunderbird 153
task

Tracking

(Not tracked)

People

(Reporter: freaktechnik, Unassigned)

References

Details

In order to properly handle aborting with the external browser OAuth flow, we need to be able to tell the server in ConfigVerifier that it should cancel whatever it's doing for the verifyLogon call. In a perfect world we might want to clean out all the nsIURI/nsIUrlListener semantics going on here (as a JS dev I'd obviously love Promises + AbortSignal but I can see that might be annoying in C++ world). This interface exists on both incoming and outgoing servers.

We'll probably also have to better expose the canceling semantics of OAuth in the XPCOM interface - since I think that's currently just used in the JS world.

This should all lead to us being able to properly abort a ConfigVerifier run, leaving us with a clean state without having to manually go in and make sure OAuth flows are cancelled etc.

You need to log in before you can comment on or make changes to this bug.