Posts Tagged ‘Certificates’

Creating a wildcard webserver certificate with your internal Microsoft CA

April 4, 2014 4 comments

It is sometimes necessary to issue a wildcard certificate from your internal Microsoft CA, I had such a requirement this week and thought it would make a nice blog post.

The post assumes you have a Enterprise CA already deployed and a web server template deployed and available for enrolment.

First we need to create the certificate request that will be issued to your CA.

1. Logon to a Windows 2008 R2 or Windows 7 domain member

2. Open the certificates MMC snap-in












Now create the certificate request

3. Right click the Certificates folder which is found under the personal folder

4. Select All Tasks > Advanced Options > Create Custom Request




5. In the Certificate Enrolment Wizard Click Next



6. In the Certificate Enrollment Page select Custom Request > Proceed without enrolment Policy and then select Next




7. In the Custom Request Page select (No template) Legacy Key from the drop down and then select Next



8.On the Certificate Information Page select the Details link, then select the Properties button



9. On the General tab complete the Friendly name field and optionally you can add a description for the certificate.




10. Select the Subject tab and fill in the relevant information as described below





Common Name


The name of the certificate. This field is used to identify the certificate. Adding the * before the domain name indicates a wildcard certificate for that domain.

Organizational Unit


The name of the OU. In most cases this is the IT department


Contoso Corp

The name of the Organization where the certificate is for.



The location of the registered location of the organization.



The County/State of your organization



The country of your organization






11. Select the Extensions tab

12. In Key usage select Digital and Key encipherment




13. On the Private Key tab set the key size to 4096 and select the option Make private key exportable.




14. Under Key type select Exchange

15. Select OK




15. On the certificate Information page select Next



16. Save the request file




That’s the certificate request file done, which was nice and easy even though there was a number of steps, we next need to use this request to generate the rest of the certificate on the CA.


17. Browse to your internal CA web enrollment pages

18. Select Request a certificate


19. Select advanced certificate request




20. Select the Submit a certificate request link




21.Open the previously created request file in notepad and copy all the data in it to clipboard.

22. Past the clipboard into the Saved Request box

23. Select the web server template

24. Click submit

25. You might get a popup box asking for confirmation, select yes




When the CA done it’s job it will offer you the ability to download the certificate

26. Select Base 64 and select Download certificate




Now back in the local machines Certificate snap-in

27. Right click the Certificates folder in the personal folder store and select import and import the file you downloaded from the CA







Now check in the certificate store you should be a valid certificate with a private key




Configure Netscaler Management for SSL with Trusted Certificate Part1

September 14, 2012 Leave a comment

So here is a scenario, you have two Citrix Netscaler VPX devices configured as a HA pair and you need to manage that pair over SSL for whatever reason. The devices are installed out of the box with a self-signed certificate which maybe fine in a dev environment but not really best practise in production. Also now with Microsoft’s Internet Explorer 10 you will find you cannot even manage the box as it no longer gives you the option to accept the untrusted certificates and continue, you will also find that this could break applications such as System Centre 2012 Virtual Machine Manager.

So what to do, well you need to get a trusted certificate but pause for a moment, you may want a little more. In this scenario we have two devices so what if you wanted to have the ability to not only logon to the active device but also the standby, well you are going to now need a certificate with Subject Alternate Names (SAN), this will enable you to connect to the device by the individual device name and the Virtual IP address shared by the devices.

Note: I am going to be using FQDN’s to access the device and not just an IP address

You need to have each nodes management name (whatever you put in the browser to get to the devise) and IP address in DNS not forgetting the shared Virtual IP.

You need to have a valid certificate, with all the FQDN’s listed as SAN’s that is trusted by all devices that will connect using SSL.

You then need to import the certificate into the Netscaler and map it to the management services.

Sounds easy, but it took me a while to put all this together.

Step 1 Get a Certificate

I am using Microsoft 2008 R2 Certificate Services and using the guide here I generate a certificate for use on the Netscalers.

1. Log on to the server as a member of the local Administrators group.

2. Click Start.

3. In the Search programs and files box, type mmc.exe, and press ENTER.

4. On the File menu, click Add/Remove Snap-in.

5. In the list of available snap-ins, click Certificates, and then click Add.

6. Click Computer account, and click Next.

7. Click Local computer, and click Finish.

8. Click OK.

9. In the console tree, double-click Certificates (Local Computer), and then double-click Personal.

10. Right-click Personal, point to All Tasks, and then click Request New Certificate to start the Certificate Enrolment wizard. (in my case Active Directory Enrollment Policy”

11. Click Next.

12. Select the Web Server template. Click the warning icon below more information is required to enroll for this certificate. Click here to configure these settings.

13. In the Subject name area under Type, click Common Name.

14. In the Subject name area under Value, enter the fully qualified domain name of the server, and then click Add.

15. In the Alternative name area under Type, click DNS.

16. In the Alternative name area under Value, enter the fully qualified domain name of the server, and then click Add.

17. Repeat steps 15 and 16 above for each additional SAN that you require.

18. On the Private Key tab ensure you enable the “Make private key exportable”

19. Click OK when finished.

20. Click Enroll

It should have looked something like the below






Checking the certificate we can see all the names listed (awesome)



We next need to export this certificate and prepare it for upload into the Netscaler devices

Click export to file and follow the wizard ensuring you select Yes to exporting the file and Include all certificates in the certification path id possible. The end result you will have a pfx file.

This file is no good for the Netscaler as it want a PEM file so we need to convert it.

Part 2