Difference between revisions of "Category:Community Sandbox"

(Replaced content with "Use this page to identify user pages, notes, rants, ideas, questions, and other Zimbra related community material. '''''Note:''' Technical articles about Zimbra products...")
 
(33 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=JDunphy Letsencrypt - Another Method Using acme.sh to Generate Certs=
+
Use this page to identify user pages, notes, rants, ideas, questions, and other Zimbra related community material.
{{KB|{{Unsupported}}|{{ZCS 8.8}}|{{ZCS 8.7}}|{{ZCS 8.6}}|}}
 
{{WIP}}
 
= Introduction =
 
Letsencrypt is a free, automated, and open Certificate Authority to generate all your PKI certificates so a browser can see & display that trusted green secure lock for your domains. Instead of installing a development environment like other Letsencrypt methods, this article describes a single bash script and can be installed and operated without being root.  Here is how to get Zimbra up and running with your Letsencrypt certificate.
 
= Requirements (1 time only)=
 
# Install acme.sh bash script in your home directory. Ref: https://github.com/Neilpang/acme.sh
 
<pre>
 
% curl https://get.acme.sh | sh
 
Or:
 
% wget -O -  https://get.acme.sh | sh
 
</pre>
 
  
Note: This will do three things.
+
'''''Note:''' Technical articles about Zimbra products that are not part of a User Page or page of notes should not be labeled with this category.''
# create a directory ~/.acme.sh
 
# update your .cshrc and .bashrc so that script is in your path
 
# create a cron job for the local user for automatic renewal
 
 
 
= Issue Your Certificate =
 
Letsencrypt needs to verify you have control of your domains before they will sign your certificate. To do that, we complete a challenge and prove we have control of the domains using their acme protocol. The acme.sh script supports all challenge methods but for this article we will focus on the Automatic DNS challenge. See https://github.com/Neilpang/acme.sh for other methods or my own documentation https://github.com/JimDunphy/deploy-zimbra-letsencrypt.sh/tree/master/Recipies/SingleServer which lists 3 different type of DNS methods. All methods that acme.sh supports work with this article.
 
 
 
When using the '''Automatic DNS Method''' for the first time,  you will need to update '''~/.acme.sh/account.conf''' to contain your DNS provider api key. A list of supported DNS providers can be found at ~/.acme.sh/dnsapi. In this article we will use CloudFlare. Login to your CloudFlare account to get your API key before proceeding and then add these 2 lines to your '''~/.acme.sh/account.conf file'''
 
 
 
# SAVED_CF_Key= '......Your API key..........'
 
# CF_EMAIL='XXXX@example.com'
 
 
 
From now on, anytime we need a certificate or renew a certificate we can do the following:
 
<pre>
 
acme.sh --issue --dns dns_cf -d mail.example.com
 
</pre>
 
If we have multiple domains associated with our Zimbra server, then it works like this:
 
<pre>
 
acme.sh --issue --dns dns_cf -d mail.example.com -d mail.example.net -d mail.example.org
 
</pre>
 
Wild card certs are supported with ACME v2 protocol
 
<pre>
 
acme.sh --issue --dns dns_cf -d mail.example.com -d '*.example.com'
 
</pre>
 
Your certificates can be found at: ~/.acme.sh/mail.example.com ... It uses the first '-d' name to create a directory to store your certificates
 
 
 
= Install Certificate With Zimbra =
 
Regardless of which challenge method you used with the acme.sh bash script, the following commands will install it. Note: I have also created a script to perform these steps automatically at https://github.com/JimDunphy/deploy-zimbra-letsencrypt.sh and the forums have a thread on this method https://forums.zimbra.org/viewtopic.php?f=15&t=60781 for additional background information. For this article we walk through those steps.
 
 
 
= Step 1 (Append IdentTrust CERT to fullchain)
 
<pre>
 
cd ~/.acme.sh/example.com
 
echo '-----BEGIN CERTIFICATE-----
 
MIIDSjCCAjKgAwIBAgIQRK+wgNajJ7qJMDmGLvhAazANBgkqhkiG9w0BAQUFADA/
 
MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT
 
DkRTVCBSb290IENBIFgzMB4XDTAwMDkzMDIxMTIxOVoXDTIxMDkzMDE0MDExNVow
 
PzEkMCIGA1UEChMbRGlnaXRhbCBTaWduYXR1cmUgVHJ1c3QgQ28uMRcwFQYDVQQD
 
Ew5EU1QgUm9vdCBDQSBYMzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEB
 
AN+v6ZdQCINXtMxiZfaQguzH0yxrMMpb7NnDfcdAwRgUi+DoM3ZJKuM/IUmTrE4O
 
rz5Iy2Xu/NMhD2XSKtkyj4zl93ewEnu1lcCJo6m67XMuegwGMoOifooUMM0RoOEq
 
OLl5CjH9UL2AZd+3UWODyOKIYepLYYHsUmu5ouJLGiifSKOeDNoJjj4XLh7dIN9b
 
xiqKqy69cK3FCxolkHRyxXtqqzTWMIn/5WgTe1QLyNau7Fqckh49ZLOMxt+/yUFw
 
7BZy1SbsOFU5Q9D8/RhcQPGX69Wam40dutolucbY38EVAjqr2m7xPi71XAicPNaD
 
aeQQmxkqtilX4+U9m5/wAl0CAwEAAaNCMEAwDwYDVR0TAQH/BAUwAwEB/zAOBgNV
 
HQ8BAf8EBAMCAQYwHQYDVR0OBBYEFMSnsaR7LHH62+FLkHX/xBVghYkQMA0GCSqG
 
SIb3DQEBBQUAA4IBAQCjGiybFwBcqR7uKGY3Or+Dxz9LwwmglSBd49lZRNI+DT69
 
ikugdB/OEIKcdBodfpga3csTS7MgROSR6cz8faXbauX+5v3gTt23ADq1cEmv8uXr
 
AvHRAosZy5Q6XkjEGB5YGV8eAlrwDPGxrancWYaLbumR9YbK+rlmM6pZW87ipxZz
 
R8srzJmwN0jP41ZL9c8PDHIyh8bwRLtTcm1D9SZImlJnt1ir/md2cXjbDaJWFBM5
 
JDGFoqgCWjBH4d1QB7wCCZAA62RjYJsWvIjJEubSfZGL+T0yjWW06XyxV3bqxbYo
 
Ob8VZRzI9neWagqNdwvYkQsEjgfbKbYK7p2CNTUQ
 
-----END CERTIFICATE-----' >> fullchain.cer
 
</pre>
 
Because zmcertmgr will chdir during install which can abort when permissions are incorrect in some circumstances, we do the following.
 
<pre>
 
% cd .acme.sh/mail.example.com
 
% cp mail.example.com.key mail.example.com.cer fullchain.cer /tmp
 
</pre>
 
 
 
= Note:
 
For version 8.7 and above, zmcertmgr runs as zimbra. For all earlier versions you will run zmcertmgr as root. Example below is for 8.7 and 8.8 versions.
 
 
 
= Step 2 Verify your certificate
 
<pre>
 
% su - zimbra
 
% cd /tmp
 
% /opt/zimbra/bin/zmcertmgr verifycrt mail.example.com.key mail.example.com.cer fullchain.cer
 
</pre>
 
 
 
If there were no errors, you can install the certificate
 
 
 
= Step 3 Install your certificate
 
<pre>
 
% su - zimbra
 
% cd /tmp
 
% cp mail.example.key /opt/zimbra/ssl/zimbra/commercial/commercial.key
 
% /opt/zimbra/bin/zmcertmgr deploycrt comm mail.example.cer fullchain.cer
 
</pre>
 
 
 
If there were no errors, proceed to restart zimbra
 
 
 
= Step 4 Restart Zimbra
 
<pre>
 
% su - zimbra
 
% zmcontrol restart
 
</pre>
 

Latest revision as of 15:02, 1 July 2019

Use this page to identify user pages, notes, rants, ideas, questions, and other Zimbra related community material.

Note: Technical articles about Zimbra products that are not part of a User Page or page of notes should not be labeled with this category.

Subcategories

This category has the following 2 subcategories, out of 2 total.

Pages in category "Community Sandbox"

The following 200 pages are in the current category.

(previous page) (next page)

A

(previous page) (next page)
Jump to: navigation, search