Difference between revisions of "Yutaka-Notes about Extensible Classes In ZimbraStore"

(com.zimbra.cs.lmtpserver.LmtpCallback)
Line 13: Line 13:
  
 
[Note] You have to register this to com.zimbra.cs.service.AuthProvider
 
[Note] You have to register this to com.zimbra.cs.service.AuthProvider
 +
 +
==com.zimbra.cs.security.sasl.Authenticator==
 +
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.
 +
 +
Sample is here;
 +
com.zimbra.cs.security.sasl.PlainAuthenticator
 +
 +
[Note] You have to register this to =com.zimbra.cs.security.sasl.Authenticator

Revision as of 01:47, 12 August 2011

com.zimbra.cs.lmtpserver.LmtpCallback

By this, you can register your custom function to be called when a messege is receive with lmtp.

Sample is here;com.zimbra.cs.mailbox.QuotaWarning

[Note]You have to register this to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend

com.zimbra.cs.service.AuthProvider

By this, you can implement to genearate custom auth token and to validate that.

Sample is here; com.zimbra.cs.service.ZimbraAuthProvider

[Note] You have to register this to com.zimbra.cs.service.AuthProvider

com.zimbra.cs.security.sasl.Authenticator

By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.

Sample is here; com.zimbra.cs.security.sasl.PlainAuthenticator

[Note] You have to register this to =com.zimbra.cs.security.sasl.Authenticator

Jump to: navigation, search