Password manager Pro RDP gateway doesn’t work

Having successfully configured the web portal to use SSL and a certificate issued by my internal CA infrastructure I thought I was home and dry with this product.

The very next issue was getting the RDP gateway working.  PMP uses a web portal sitting on port 7273 to provide an RDP and SSH client to the PMP user.  It’s a great idea but when I tried to use it the tab was closed immediately.  I say immediately what happens is you get a popup message box asking if it’s OK to shut the tab. It doesn’t matter what you click it won’t work.

On the password tab there is a hyperlink “Trouble Shoot Auto Logon Issues” click this and another browser ( with no URL bar ) opens and displays a certificate error.  Unfortunately you can;’t view the cert and the error doesn’t really tell you what the problem is.  THATS USEFUL MICROSOFT!

I used Chrome and that allowed me to see the certificate.  BOOM!  it’s self signed and that’s why it’s not working.

So why oh why doesn’t ManageEngine tell you how to configure the RDP gateway to use the same certificate as the web portal?

The fix ( provided by ManagedEngine by the way ) is to edit the wrapper.conf file in the <PMP Install Directory>conf folder.

(Make a copy first in case you mess this up of course)  You need to locate the following elements and change them to reflect the certificate.

wrapper.java.additional.21=-Djavax.net.ssl.keyStore=../conf/server.keystore  change server.keystore to your .pfx file created in my other post.

wrapper.java.additional.22=-Djavax.net.ssl.keyStorePassword=passtrix  and change passtrix to the password you used to secure the private key in the .pfx file.

wrapper.java.additional.23=-Djavax.net.ssl.keyStoreType=<keyType> change this to PKCS12

Restart PMP and it should all start working.  MAGIC!

Advertisements

Configuring SSL for PasswordManagerPro

The PasswordManagerPro web site lists the following FAQ on how to setup an SSL certificate that is signed by a trusted Certificate Authority.

https://www.manageengine.com/products/passwordmanagerpro/faq.html#ssl

However this discusses the use of either KeyTool or OpenSSL, neither of which are installed on a windows server and the article does not discuss the use of a Microsoft CA which surely is a very common deployment scenario?

I worked on this for quite a while getting quite frustrated with the poor instructions provided in the FAQ.  Once solved, the solution is amazingly easy and I thought it worth blogging about it.

Step 1: Create a certificate template that allows you to export the private key. 

Logon to the CA and launch the certificate authority MMC
launchCA

Manage the certificate templates

ManageTemplates

Duplicate template , web server certificate as a Windows Server 2008 Enterprise template and give the template a new Name, I called mine PMP in my test lab.

Edit the template security to allow the PMP server to request a certificate

permissions

On the request handling tab check “allow private key to be exported” and click OK to save the template

requesthandling

Close the “manage template” window and then publish the certificate template to the CA by right clicking in the certificate template pane and selecting  New\Certificate Template to Issue

templatetopublish1

Select the template you just created and click OK

Log off the CA

Step 2: Issue the certificate to the PMP server.

Logon to the PMP server and open a new MMC

Add the certificates template to the MMC and target the computer account.

AddCertMMC

addMMCsnapin1

addMMCsnapin2

addlocalcomp

Request a new certificate in the computers personal store

reqNewCert

Click Next on the welcome screen and Next on the enrolment screen

Select the template you created in step 1

request1

Add the Alternative name as the DNS name of the server
alternatesubname

Add a friendly name and description to help identify the certificate later when exporting it
certName

Click Enroll

enroll

Step 3: Export the certificate and it’s private key

Click next on the welcome screen and select the “Yes, export the private key” radio button and click Next.

exportkey

Accept the defaults and click next

Check the “Password” box and enter a password – this password will be used when configuring the PMP web service so make sure you record this securely.  We can even store a copy of this key in the PMP configuration of course.

export2

Set the output filename

outfilename

Click finish to export the certificate with the associated private key

summary

Step 4: Configure PMP to use the new certificate.

Stop the PMP service if it’s running

Copy the exported certificate file to the PMP/conf folder

Make a copy of the existing server.xml so you can roll back to the previous version if you need to

Edit the server.xml as follows

Locate the line keyword  keystoreFile=”conf/server.keystore” keystorePass=”passtrix”

Change it to use the certificate you exported in step 2.

keystoreFile=”conf/test22.pfx” keystorePass=”Password8″

add the keystoreType just after the keystorePass attribute

keystoreType=”PKCS12″

Save the file

Start the PMP server

If you followed the procedure correctly then the server will start and when you connect, using the DNS name of the server, the new trusted certificate will be used and you won’t see the cert error any more.

That’s all folks!