How to make an Enterprise certification authority that is running Windows Server 2003 with Service Pack 1 or an x64-based version of Windows Server 2003 compliant with ISIS-MTT version 1.1
This article has been archived. It is offered "as is" and will no longer be updated.
If you want to make an Enterprise certification authority (CA) compliant with the ISIS-MTT version 1.1 standard, follow the steps that are described in this article. The issuing CA must force UTF-8 encoding. After a certificate request is submitted, the key usage attribute must be marked "critical" during the certificate submission process. You can then issue and verify the certificate.
IN THIS TASK
ISIS-MTT is a new German standard for Public Key Infrastructure (PKI) interoperability. ISIS-MTT defines data formats and communication protocols to be employed in interoperable PKI-based applications. ISIS-MTT specifications focus on security services for authentication. These include user identification and data integrity services, confidentiality services, and non-repudiation services. The ISIS-MTT standard was developed by the German government in collaboration with banking, industrial, and academic interests.
To make the Microsoft Windows certification authority (CA) compliant with ISIS-MTT version 1.1, you must complete specific configuration steps. This step-by-step article describes how to enroll certificates that comply with the ISIS-MTT requirements for an Enterprise CA.
Note Your CA must be a server that is running Microsoft Windows Server 2003 Service Pack 1 (SP1), an x64-based version of Windows Server 2003, or a later version of Windows.
Important The configuration changes that are documented in this article must be applied to the CA that enrolls the certificate. In a PKI topology, this is the parent CA of the certificate requester. If a CA certificate is requested from a subordinate CA, the type of CA that requests the certificate is not relevant.
Use the step-by-step directions in this article if the following conditions are true:
- The issuing CA issues ISIS-MTT-compliant certificates to subordinate CAs or to end-entities.
- The issuing CA takes one of the following roles:
- Enterprise root CA
- Enterprise subordinate CA
- Configure the issuing CA to force UTF8 encoding.
- Mark the key usage attribute as "critical" during certificate submission processing.
- For CA certificates, click to clear the Digital signature attribute to change the key usage.
Enforce UTF8 encodingAfter you configure a CA to force UTF8 encoding, the UTF8 setting applies to all certificates that are issued with this CA. At the CA that must issue ISIS-MTT-compliant certificates, follow these steps:
- Click Start, click Run, type cmd, and then click OK.
- Type the following, and then press ENTER: certutil -setreg ca\forceteletex +0x20This command sets the flag so that the CA always encodes the subject with UTF8.
- To stop and to restart the CA service, type the following at a command prompt. Press ENTER after each command.net stop "certificate services"net start "certificate services"
- Type the following at a command prompt, and then press ENTER: certutil -setreg ca\forceteletex -0x20
- To stop and to restart the CA service, type the following commands. Press ENTER after each command.net stop "certificate services"net start "certificate services"
back to the top
Configure the certificate template to change the key usage and to mark it as "critical"When certificates are issued with an Enterprise CA, you must set the critical flag through the certificate template that is used for certificate creation. By default, CA certificate requests use the Subordinate Certification Authority certificate template. Certificates for a user or for a computer are processed in one of the following ways:
- Through the template that is specific to the certificate request.
- During the certificate submission process.
- On the issuing CA, click Start, click Run, type mmc, and then click OK.
- On the File menu, click Add/ Remove Snap-in.
- On the Standalone tab, click Add.
- In the Available Standalone Snap-ins list, click Certificate Templates, click Add, and then click Close.
- Click OK, and then click Certificate Templates.
- In the right-pane, right-click Subordinate Certification Authority, and then click Duplicate Template.
- On the General tab, type SubCAcritical in the Template display name box, and then click OK.
- Double-click SubCAcritical, click the Extensions tab, click Key Usage, and then click Edit.
- Click to select the Make this extension critical check box, click to clear the Digital signature check box, and then click OK.
- Click the Issuance Requirements tab, and then click to select the CA certificate manager approval check box.
Note This step is optional. However, we recommend that you use this option to help you keep track of the CA certificates that are issued.
- If you require any other customized options in the template, make these changes now, and then click OK.
- Click Start, point to Administrative Tools, and then click Certification Authority.
- Expand Your_CA, right-click Certificate Templates, point to New, and then click Certificate Template to Issue.
- In the Select one or more Certificate Templates to enable on this Certification Authority list, click SubCAcritical, and then click OK.
- Repeat steps 6 through 14 to configure the key usage setting for user or computer certificates.
Request a CA certificate for a subordinate CAIn a multi-tier PKI topology, a subordinate CA can request the CA certificate online or offline. By default, the Subordinate Certification Authority setting is always used when a request is made online. Therefore, the key usage settings are not applied. When a subordinate CA requests the CA certificate, you must complete the request offline so that you can specify the template name.
To issue a certificate for a subordinate CA, follow the steps in the "Submit the certificate request" section.
Note According to the ISIS-MTT standard, the name of a CA must contain the following distinguished name attributes:
- countryName (c)
- organizationName (o)
back to the top
Submit the certificate requestTo enroll a certificate with a specific certificate template, you must set the template name during the certificate submission process by using the Certreq.exe command.To do this, follow these steps:
- Click Start, click Run, type cmd, and then click OK.
- Type the following, and then press ENTER: certreq submit attrib CertificateTemplate:SubCAcritical [RequestFileIn]Notes
- If you used a different template name when you configured the certificate template, replace "SubCAcritical" with the template name that you used.
- Alternatively, you can request the certificate through the Web-enrollment Web pages, instead of using the Certreq.exe command.
- If certificate approval was configured, issue the pending CA request. To do this, expand the Pending Requests folder, click the certificate request, point to All Tasks on the Action menu, and then click Issue.
- Make the certificate available to the user who is requesting the certificate by exporting the certificate from the certificates database. To do this, follow these steps:
- Click the Issued Certificates container.
- Click the newly issued CA certificate in the right pane, click Action, and then click Open.
- Click the Details tab, and then click Copy to File.
- On the Welcome to the Certificate Export Wizard page, click Next.
- Click Cryptographic Message Syntax Standard – PKCS #7 Certificates (.P7B), click to select the Include all certificates in the certification path if possible check box, and then click Next.
- In the File name box, type a file name for the saved CA certificate, and then click Next. The Export Wizard automatically adds a file name extension to the file name.
- On the Completing the Certificate Export Wizard page, click Finish.
- In the Certificate Export Wizard dialog box, Click OK.
Technical support for Windows x64 editionsYour hardware manufacturer provides technical support and assistance for Microsoft Windows x64 editions. Your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.
For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:
For additional information about how to use ISIS-MTT compliant certificates with a stand-alone issuing CA, click the following article number to view the article in the Microsoft Knowledge Base:
888180 How to make a stand-alone certification authority that is running Windows Server 2003 with Service Pack 1 compliant with ISIS-MTT version 1.1back to the top
Winx64 Windowsx64 64bit 64-bit
Article ID: 890772 - Last Review: 12/09/2015 01:57:30 - Revision: 2.4
Microsoft Windows Server 2003 Service Pack 1, Microsoft Windows Server 2003, Datacenter x64 Edition, Microsoft Windows Server 2003, Enterprise x64 Edition, Microsoft Windows Server 2003, Standard x64 Edition
- kbnosurvey kbarchive kbwinservds kbactivedirectory kbcertservices kbhowtomaster KB890772