Atlassian Bitbucket
Bitbucket is a software developped by Atlassian and I define it like an interface to Git, in order to make it more friendly.There is a bunch of software in Bitbucket, acting as layers in order to facilitate collaboration on code.
Last but not least, Bitbucket has a good integration with Jira, which is one of the main reasons I choosed it to be our tool at ESTI.
I thank Atlassian very much for metting ESTI use community licence of both Jira and Bitbucket.
The goal: HTTPS and SSH on regular ports
Default HTTP and SSH port for Bitbucket is neither 443 nor 22. Their are configurable and it would be possible to directly make Bitbucket face those ports, but we dont like that, we'd rather setup a HAProxy instance that will forward the ports for us.Prerequisite for that is to have a HTTPS certificate. It might be self signed or not. The one I use is not self-signed, and I bought it to Gandi, which provides an intermediate SHA2 certificate.
To sum it up, I have in my hand:
- The private key I used to request the certificate: rktmb.org.key
- The certificate for the domain: rktmb.org.crt
- The intermediate Gandi certificate: gandi.pem
Configure HAProxy for HTTPS
Configuring HAProxy to make SSL termination sur Bitbucket is already documented on Atlassian Website. Pointing to that very good documentation is essential, but it misses one point: how to build the certificate that HAProxy need in order to trigger the SSL handshake?As you can see in the sample configuration file, there is a "crt /etc/haproxy/certAndKey.pem" in the configuration and there is no indication is given on how to build it. We are going to fill that point here.
In HAProxy, the "crt" option has a unique value, which is a filename, hich points to the certificate issued by the authority you bought the certificate from. But it is not that simple: It should be in fact the concatenation of the "private key" and the "certificate". If you notice in the Atlassian documentation linked above, the name is "certAndKey.pem".
You build it with:
# cat rktmb.org.crt rktmb.org.key > certAndKey.pem
But if you ever need to use an intermediate certificate, this usually happens on some old browsers, the "certAndKey.pem" file then become a "cert_inter_private.pem" file, which is composed of the concatenation of the "private key" the "intermadiate" and the "certificate".
You buid it with:
# cat rktmb.org.crt gandi.pem rktmb.org.key > rktmb.org.cert_inter_private.pem