| UID | title | description | helpviewer_keywords | old-location | tech.root | ms.assetid | ms.date | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | req.redist | ms.custom | f1_keywords | dev_langs | topic_type | api_type | api_location | api_name | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NF:xenroll.IEnroll.createFilePKCS10WStr |
IEnroll::createFilePKCS10WStr (xenroll.h) |
Creates a base64-encoded PKCS (IEnroll.createFilePKCS10WStr) |
|
security\ienroll4_createfilepkcs10wstr.htm |
security |
5edd54c5-9dfb-44b8-a293-4fe6a8de45e3 |
12/05/2018 |
IEnroll interface [Security],createFilePKCS10WStr method, IEnroll.createFilePKCS10WStr, IEnroll::createFilePKCS10WStr, createFilePKCS10WStr, createFilePKCS10WStr method [Security], createFilePKCS10WStr method [Security],IEnroll interface, security.ienroll4_createfilepkcs10wstr, xenroll/IEnroll::createFilePKCS10WStr |
xenroll.h |
Windows |
Windows XP [desktop apps only] |
Windows Server 2003 [desktop apps only] |
Uuid.lib |
Xenroll.dll |
Windows |
19H1 |
|
|
|
|
|
|
[This method is no longer available for use as of Windows Server 2008 and Windows Vista.]
The createFilePKCS10WStr method creates a base64-encoded PKCS #10 certificate request and saves it in a file. This method was first defined in the IEnroll interface.
This method differs from the createPKCS10WStr method only in saving the base64-encoded PKCS #10 certificate request to the file specified by the wszPKCS10FileName parameter.
The distinguished name (DN) of the entity for which the request is being made. DNName must follow the X.500 naming convention. For example, "CN=User, O=Microsoft". If a two-letter prefix does not exist, an object identifier (OID) may be provided instead.
An OID that describes the purpose of the certificate being generated, for example, individual or commercial Authenticode certificate, or client authentication. You can also specify multiple OIDs separated by a comma.
The OID is passed through to the PKCS #10 request. The control does not examine the OID.
The name of the file in which the base64-encoded PKCS #10 is saved. The contents of this file may be submitted to a certification authority for processing.
By default, the Microsoft Base Cryptographic Provider is used, and a unique signature key is created.