CLI zmtlsctl to set Web Server Mode: Difference between revisions
mNo edit summary |
m (→Steps to run) |
||
Line 60: | Line 60: | ||
-As a quick fix, when 'both' was selected, it defaulted to 'mixed' [http://bugzilla.zimbra.com/show_bug.cgi?id=5594 bug 5594] | -As a quick fix, when 'both' was selected, it defaulted to 'mixed' [http://bugzilla.zimbra.com/show_bug.cgi?id=5594 bug 5594] | ||
-As of 5.0.5+ [http://bugzilla.zimbra.com/show_bug.cgi?id=5594 bug 5594] is now resolved | -As of 5.0.5+ [http://bugzilla.zimbra.com/show_bug.cgi?id=5594 bug 5594] is now resolved so both mode works properly. | ||
[[Category:Command Line Interface]] | [[Category:Command Line Interface]] |
Revision as of 19:55, 15 April 2009
zmtlsctl
This command is used to set the Web server zimbraMailMode to the different communication protocol options. All modes use SSL encryption for back-end administrative traffic & the admin console.
The webserver has to be stopped and restarted for the change to take effect. Though a full zmcontrol stop/start certainly can't hurt.
Syntax
zmtlsctl [mode]
Mode choices:
http - http only, the user would browse to http://zimbra.domain.com
https - https only, the user would browse to https://zimbra.domain.com http:// is denied.
mixed - If the user goes to http:// it will switch to https:// for the login only, then will revert to http:// for normal session traffic. If they browse to https:// then they will stay https://
both - A user can go to http:// or https:// and will keep that mode for their entire session.
redirect - Added to ZCS 5.0; Like mixed if the user goes to http:// it will switch to https:// but they will stay https:// for their entire session.
(See also Redirect_http_to_https for 4.5)
Steps to run
1. |
Type zmtlsctl [mode] , press Enter. |
2. |
Type zmcontrol stop , press Enter. |
3. |
after everything stops, type zmcontrol start , press Enter. |
Note: In you can also use tomcat stop/start/restart, but in v5 this becomes jetty (zmmailboxdctl stop/start/restart).
Afterwards: Check SMTP_Auth_Problems to be sure the auth url is set correctly.
Quirks
-On older versions there were some quirks with 'both' mode; fine from 4.5.2 to 4.5.5? but new issue appeared bug 19636
-As a quick fix, when 'both' was selected, it defaulted to 'mixed' bug 5594
-As of 5.0.5+ bug 5594 is now resolved so both mode works properly.