Today for another issue already addressed increase zimbra session timeout :
Administrators of beehive currently have to educate their users that their Zimbra sessions are killed after a fixed timeout (in our case, we set it to be one hour), regardless of their activity. This is really awkward, and we are waiting for implementation of
ER 9206754: ZIMBRA TIMEOUT SESSION VALUE (this was approved for future release, but without version info).
Please second this enhancement request to further its timely implementation.
And as always: please do partake in this beehive forum, as buzz-free does not mean fuzz-free in the beekeepers beehive!
MOS Note 1080918.1 states that Zimbra timeouts
are really no Idle Timeouts:
(How to adjust Zimbra and JSSO Timeout in Beehive Release 2):
SSO session timeout (in seconds) when the SSO Provider is
JavaSSO. Note that this is a hard timeout, not an inactivity
timeout. The session will timeout after this amount of time no
As any Zimbra user of beehive should be bothered by this, please do second ER 9206754 through MOS.
Christmas is near - so it's time to collect wishes!