1. 21 Mar, 2018 1 commit
  2. 20 Feb, 2018 1 commit
  3. 25 Jan, 2018 1 commit
  4. 28 Nov, 2017 1 commit
  5. 17 Oct, 2017 1 commit
  6. 12 Oct, 2017 1 commit
  7. 03 Oct, 2017 1 commit
    • Malte S. Stretz's avatar
      Update the default value of JAVA_BINARY · 3870e1bf
      Malte S. Stretz authored
      The location of the Zimbra Java binary changed from /opt/zimbra/java/bin/java
      to /opt/zimbra/common/bin/java.  So when building zmmailboxdmgr you have to
      provide the new path to the Makefile to make it work.  There is an override to
      do so in zm-build but since the Java binary will probably stay where it is
      now, this patch changes the default path as well.
      3870e1bf
  8. 02 Oct, 2017 1 commit
  9. 18 Sep, 2017 2 commits
  10. 28 Aug, 2017 1 commit
  11. 18 Aug, 2017 1 commit
    • Shriram V's avatar
      ZCS:2486 - Separated jetty.base and jetty.home, removed jetty-<version> · cb6c59a1
      Shriram V authored
      - Zimbra's Jetty Distribution (9.3.5.v20151012) is installed in /opt/zimbra/common/jetty_home/ via a separate package.
      - Zimbra specific webapps and other custom jetty configuration files will be installed in /opt/zimbra/jetty_base/.
      - Now /opt/zimbra/mailboxd and /opt/zimbra/jetty are symbolic links that point to /opt/zimbra/jetty_base/.
      cb6c59a1
  12. 04 Jan, 2017 1 commit
  13. 26 Dec, 2016 2 commits
  14. 29 Jun, 2016 3 commits
  15. 28 Jun, 2016 3 commits
  16. 24 Jun, 2016 3 commits
  17. 23 Jun, 2016 1 commit
  18. 22 Jun, 2016 3 commits
  19. 21 Jun, 2016 1 commit
  20. 17 Jun, 2016 3 commits
  21. 16 Jun, 2016 1 commit
  22. 14 Jun, 2016 3 commits
  23. 13 Jun, 2016 4 commits
    • Quanah Gibson-Mount's avatar
      Integrated the following from //depot/zimbra/JUDASPRIEST/...: · 3d39c2d5
      Quanah Gibson-Mount authored
      Change 572284 by quanah@qint on 2016/06/13 19:28:05
      
      Integrated the following from //depot/zimbra/main/...:
      Change 572283 by quanah@qmain on 2016/06/13 19:27:57
      
      bug: 105079
      Update libxml2 version
      
      https://bugzilla.zimbra.com/show_bug.cgi?id=105079
      
      Copied from Perforce
       Change: 572285
      3d39c2d5
    • Quanah Gibson-Mount's avatar
      Integrated the following from //depot/zimbra/main/...: · 0132b62a
      Quanah Gibson-Mount authored
      Change 572283 by quanah@qmain on 2016/06/13 19:27:57
      
      bug: 105079
      Update libxml2 version
      
      https://bugzilla.zimbra.com/show_bug.cgi?id=105079
      
      Copied from Perforce
       Change: 572284
      0132b62a
    • Quanah Gibson-Mount's avatar
      Integrated the following from //depot/zimbra/JUDASPRIEST/...: · fa6e9fae
      Quanah Gibson-Mount authored
      Change 572262 by raykini@raykini-main on 2016/06/13 15:20:27
      
      Bug: 105057
      
      This bug is caused by login servers not having a consistent view of the zimbraTwoFactorAuthEnabled attribute. If 2FA is set up on server1, and a subsequent login request lands on server2 before the 15 minute cache expiry is reached, the user will not be prompted for a second factor. 
      
      The fix is to invalidate the cache entry for this account on all login servers whenever 2FA is enabled or disabled. This will force subsequent login requests to get the latest attribute value from LDAP. This is done asynchronously in the new static clearAccountCacheOnLoginServers() method of ZimbraTwoFactorAuth. Since FlushCacheRequest is an admin request, it is authenticated using the internal admin auth provided by SoapProvisioning.
      
      It should be noted that this bugfix can result in heavy loads on the login servers and on LDAP in the theoretical edge case where a large number of users enable or disable 2FA at the same time. That said, this scenario should be highly unlikely since the EnableTwoFactorAuth and DisableTwoFactorAuth endpoints are rarely invoked by an individual user.
      
      ZimbraTwoFactorAuth.java:
      - added new method clearAccountCacheOnLoginServers that asynchronously sends a FlushCache request for the given account to all servers specified by zimbraReverseProxyUpstreamLoginServers.
      - added new static ExecutorService "ClearLoginServerAccountCache"
      
      EnableTwoFactorAuth.java, DisableTwoFactorAuth.java:
      - call ZimbraTwoFactorAuth.clearAccountCacheOnLoginServers after successful enablement/disablement of 2FA
      
      https://bugzilla.zimbra.com/show_bug.cgi?id=105057
      
      Copied from Perforce
       Change: 572275
      fa6e9fae
    • Quanah Gibson-Mount's avatar
      Integrated the following from //depot/zimbra/JUDASPRIEST-870/...: · 78775399
      Quanah Gibson-Mount authored
      Change 572269 by quanah@qint on 2016/06/13 17:04:14
      
      bug: 97654
      Update copyright and license
      
      https://bugzilla.zimbra.com/show_bug.cgi?id=97654
      
      Copied from Perforce
       Change: 572274
      78775399