Jesper Kiær has posted a very compelling video showing how the HTTPEnableConnectorHeaders = 1 notes.ini parameter can be used to gain access to Domino servers.
We no longer use the Apache proxy scheme as the SSL support in Domino has improved but I tested this on one of our development servers by setting HTTPEnableConnectorHeaders = 1 and using the “Modify Headers for Google Chrome” extension and was able to get access.
As Jesper notes many of the write ups about using Domino behind a proxy ( including mine ) specify using this setting. There are some useful comments to the first post in Jespers series on this issue.
Last year IBM got into a bit of a pickle when the Poodle Exploits hit and there was no support for SSLV3 in domino. At the time we moved to putting Apache Proxy Servers in front off all of our web facing servers.
I needed to deploy a new XWorks server for a customer or our “Knowledge Directory” product and we wanted to do some LDAP integration. As the Apache Proxy servers only do HTTP traffic and not LDAP or SMTP I though that I would try the native Domino SSL / TLS functionality again.
My impressions were pretty good. I was able to take an existing Apache SSL certificate and change it into a Domino KYR format certificate without too much hassle. It did take time ( about 2 hours ) but the next time around it would only take 30 minutes.
The KYRtool is a command line tool but following my experiences of doing it for the Apache servers last year it was no more difficult than that platform.
Update : XPages has stopped working on the server that I applied this fix to. This may be a total red herring and specific to my server but I though I should mention it. The server was 853 FP3 and I went to FP3 FP6 and then IF4. It is on CentOS and gets hacked about a bit as it is an internal dev server so it may not be typical. i will look at it again tomorrow. For now I have reinstalled 853 and all seems well – apart from no TLS obviously
Just deployed FP6 IF 4 to a production grade system and all went well – < 10 mins down time
IBM has released fix packs to allow SMTP mail to be routed via TLS 1.0 rather than SSL V3 to eliminate the Poodle vulnerability. It is very straight forward to apply. The fix pack also covers HTTP traffic too so no more Apache Reverse Proxy servers unless you want them for other reasons.
Over the last week or so I have been moving to using an Apache server in front of my Domino servers. This has been working really well until I had a problem with Mark Leusink’s Auto Login’s module
The code includes some code that calls a url constructed as
The Apache rewrite engine returns this as
whereas Domino would normally return
The solution ( via Tytus Kurek ) is to use the NE attribute in the rewrite rules as shown below.
This attribute preserves special characters such as ? and &
Interestingly in examining what was going on it does seem as though url is being called using HTTP rather than the HTTPS protocol – I need to look into that further. This does mean that the attribute needs to be added to both the httpd.conf and the /etc/httpd/conf.d/ssl.conf files. I have updated my posts from the weekend.
Hopefully this change will not affect any other functionality – I will post if it does.
Thankfully this post is now obsolete – see this IBM article which includes a modern tool to manage the Keyrings
Note that the easiest option to install a verified SSL certificate into the Apache server is to buy a new one. However, if you have a copy of Windows XP handy you can convert your existing Domino SSL certificates to Apache certificates with the following scheme.
Many thanks to Darren Duke who helped get me started with this scheme via a post on his blog about a different but overlapping scenario.
Step 0 – Why do I need to do this
Essentially you need to get your private key because Apache needs it to verify the SSL certificate,
When you originally requested your verified SSL certificate from your SSL vendor you gave them a CSR which was created via the Domino Server Certificate Administration database.
This generated a private key and used that to create the CSR request.
The SSL provider took this and using their own encryption key created the SSL certificate. This certificate will only work in the presence of your original private key and Apache cannot use the Domino .kyr file format where it is buried.
Step 1 – Install IBM ikeyman version gsk5
You need this specific version. You can download it here
It will only run on Windows XP
a) extract the zip contents to the root of the c: drive
b) Run the batch command gskregmod.bat from the command line to set some registry settings
c) Run the batch command runikeyman to open the application.
Step 2 – Extract the Private Key and Cert information from Domino the keyring KYR file
a) open the .kyr file and export it as a P12 file
Step 3 – Convert the PK12 Format file to a text file
There are two methods here.
The simple one is to use this resource but I am never happy uploading private keys to the web.
The better method is to use the OpenSSL module already stored on your server.
Use WinSCP to copy the .PK12 file to the server and then use the following command in the Linux console
>openssl pkcs12 -in example.p12 -out example.pem
You will need to give the .PK12 password and supply a new one.
You can now open the pem file as a text file and can see that it has 4 components ( this may vary )
1) Server Certificate Intermediate Certificate
this is the public key for the intermediate certificate and could have been obtained from the SSL certificate issuer’s web site
2) Certification Authority Root Certificate
this is the root public key for the intermediate certificate and could have been obtained from the SSL certificate issuer’s web site
This is your SSL certificate and was probably emailed to you when you purchased your SSL certificate ( but it is no good without the private key buried in the Domino kyr file )
4) Encrypted private key
This is what you are after. I believe that you can use it in its encrypted form but you will need to provide the password every time you start Apache. To avoid this you can store it on the server in its unencrypted form but you need to make sure it is well secured otherwise a anyone who has access to it can compromise your SSL traffic.
Read section 6.6. of this document and apply the security settings recommended
You can unencrypt the key using the following command