Open Bug 400212 Opened 17 years ago Updated 2 years ago

Refactor SASL mechanism code to common location

Categories

(MailNews Core :: Backend, defect)

defect

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: simon, Assigned: simon)

References

Details

All of the currently supported mail protocols (IMAP, POP3, SMTP) support various SASL mechanisms. Despite the fact that the SASL mechanisms are generic, there is a lot of duplicated support code between the three protocols. This makes it hard, both to add new SASL mechs, and to extend SASL support to other protocols (such as LDAP).

Three of our SASL mechanisms (NTLM, MSN and GSSAPI) are already implemented via nsIAuthModules. It should be possible to implement the remaining mechanisms as nsIAuthModules too, to generalise the processing code in each of the protocols, and to expose all of these mechanisms to the LDAP addressbook code.

I have a patch in progress which does the first stage of this refactoring - the code improvements appear pretty compelling, but if this is a really bad idea for some reason, please shout 'stop' now!
no, this sounds good. 
OS: Mac OS X → All
Hardware: PC → All
Status: NEW → ASSIGNED
Product: Core → MailNews Core
assignee=nobody, so >status=new
Status: ASSIGNED → NEW
Assignee: nobody → simon
Status: NEW → ASSIGNED
Simon are you still working on patch?
So if we got it re factored this mean we can get easily EXTERNAL SASL mechanism as well, shouldn't I fill another bug on that?
Blocks: 521952
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.