Home > Certificates, Windows 2008 R2 > Creating a wildcard webserver certificate with your internal Microsoft CA

Creating a wildcard webserver certificate with your internal Microsoft CA

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

 

image

 

image

 

image

 

image

 

image

 

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

 

image

 

5. In the Certificate Enrolment Wizard Click Next

image

 

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

 

image

 

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

image

 

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

image

 

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

 

image

 

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

 

Field

Value

Description

Common Name

*.contoso.com

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

IT

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

Organization

Contoso Corp

The name of the Organization where the certificate is for.

Location

Seattle

The location of the registered location of the organization.

State

WA

The County/State of your organization

Country

US

The country of your organization

 

image

 

image

 

11. Select the Extensions tab

12. In Key usage select Digital and Key encipherment

 

image

 

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

 

image

 

14. Under Key type select Exchange

15. Select OK

 

image

 

15. On the certificate Information page select Next

image

 

16. Save the request file

image

SNAGHTML2cebb4ae

 

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

image

19. Select advanced certificate request

 

image

 

20. Select the Submit a certificate request link

 

image

 

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

image

image

 

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

 

image

 

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

 

image

SNAGHTML2cf4fb12

image

image

 

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

 

SNAGHTML2cf6087b

Advertisements
  1. April 17, 2015 at 9:48 pm

    Doesn’t this circumvent your PKI? Why have an internal CA if you hand out a wildcard? I guess you could revoke it but only if your revocation mechanisms are working.

    • blackduke77
      June 13, 2015 at 2:39 pm

      There are some cases where you want a wildcard, I did so this article shows how I did it. PKI would not be very useful if you could not revoke a certificate

  2. Ylann Jourdren
    September 23, 2015 at 12:36 pm

    Thanks, worked perfectly!

  3. Roman
    November 18, 2015 at 2:26 pm

    Hello,
    I am trying to use your option and I generate certificate with exportable successfuly. I want to use it with IIS for our development environment where any testing webpage endings with “.hokus”. So I made *.hokus certificate but I am still getting error on accessing webpage due to different URL. Dont you know why? I also tried to add alternative name what I have seen on our normal certificate but with no luck:-/
    Any help would be appreciated!
    Thank you

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: