Skip to content

Commit 1519386

Browse files
Merge pull request #179143 from kengaderdus/resolve-ghi-83466
Resolve GitHub issue 83576 - Update Obtain a certificate procedure for Windows OS
2 parents 8f11429 + bd48374 commit 1519386

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

includes/active-directory-b2c-create-self-signed-certificate.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ If you don't already have a certificate, you can use a self-signed certificate.
1414

1515
On Windows, use the [New-SelfSignedCertificate](/powershell/module/pki/new-selfsignedcertificate) cmdlet in PowerShell to generate a certificate.
1616

17-
1. Run the following PowerShell command to generate a self-signed certificate. Modify the `-Subject` argument as appropriate for your application and Azure AD B2C tenant name. You can also adjust the `-NotAfter` date to specify a different expiration for the certificate.
17+
1. Run the following PowerShell command to generate a self-signed certificate. Modify the `-Subject` argument as appropriate for your application and Azure AD B2C tenant name such as `contosowebapp.contoso.onmicrosoft.com`. You can also adjust the `-NotAfter` date to specify a different expiration for the certificate.
1818

1919
```PowerShell
2020
New-SelfSignedCertificate `
@@ -27,11 +27,15 @@ On Windows, use the [New-SelfSignedCertificate](/powershell/module/pki/new-selfs
2727
-CertStoreLocation "Cert:\CurrentUser\My"
2828
```
2929
30-
1. Open **Manage user certificates** > **Current User** > **Personal** > **Certificates** > *yourappname.yourtenant.onmicrosoft.com*.
30+
1. On Windows computer, search for and select **Manage user certificates**
31+
1. Under **Certificates - Current User**, select **Personal** > **Certificates**>*yourappname.yourtenant.onmicrosoft.com*.
3132
1. Select the certificate, and then select **Action** > **All Tasks** > **Export**.
32-
1. Select **Yes** > **Next** > **Yes, export the private key** > **Next**.
33-
1. Accept the defaults for **Export File Format**.
34-
1. Provide a password for the certificate.
33+
1. Select **Next** > **Yes, export the private key** > **Next**.
34+
1. Accept the defaults for **Export File Format**, and then select **Next**.
35+
1. Enable **Password** option, enter a password for the certificate, and then select **Next**.
36+
1. To specify a location to save your certificate, select **Browse** and navigate to a directory of your choice.
37+
1. On the **Save As** window, enter a **File name**, and then select **Save**.
38+
1. Select **Next**>**Finish**.
3539
3640
For Azure AD B2C to accept the .pfx file password, the password must be encrypted with the TripleDES-SHA1 option in the Windows Certificate Store Export utility, as opposed to AES256-SHA256.
3741

0 commit comments

Comments
 (0)