Skip to content

Commit cb22c74

Browse files
authored
Update create-key-vault-for-code-signing.md
1 parent 30e1c33 commit cb22c74

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

powerapps-docs/maker/common/wrap/create-key-vault-for-code-signing.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -59,26 +59,26 @@ Follow these steps to create **Azure key vault** for wrap for Power Apps and con
5959

6060
5. Depending on your device follow one of the these options:
6161

62-
- For Android, create the .pfx file upload it to the keyvault certificate section. More information: [Generate keys](code-sign-android.md#generate-keys)
62+
- For Android, create the .pfx file upload it to the keyvault certificate section. More information: [Generate keys](code-sign-android.md#generate-keys)
6363

64-
:::image type="content" source="media/wrap-canvas-app/wrap-1.png" alt-text="Create a cert for Android.":::
64+
:::image type="content" source="media/wrap-canvas-app/wrap-1.png" alt-text="Create a cert for Android.":::
6565

66-
> [!NOTE]
67-
> The name of the certificate must be present in the tag step. The password also needs match the password you entered during the store pass parameter used to create the .pfx file in step 2.
66+
> [!NOTE]
67+
> The name of the certificate must be present in the tag step. The password also needs match the password you entered during the store pass parameter used to create the .pfx file in step 2.
6868
69-
- For iOS:
70-
1. Install the .cer into Keychain Access app by selecting it. More information: [Create the distribution certificate](code-sign-ios.md#create-the-distribution-certificate) </br> Then export the file as a .p12 file by right clicking your certificate file and select **Export**, and then select the file format .p12.
69+
- For iOS:
70+
1. Install the .cer into Keychain Access app by selecting it. More information: [Create the distribution certificate](code-sign-ios.md#create-the-distribution-certificate) </br> Then export the file as a .p12 file by right clicking your certificate file and select **Export**, and then select the file format .p12.
7171

7272
> [!NOTE]
7373
> The .p12 password that you set in step 4 is required when uploading it to the keyvault in the next step.
7474
75-
2. [Create the provisioning profile](code-sign-ios.md#create-an-ios-provisioning-profile) and run this command to encode it to base64:
76-
- Mac: base64 `-i example.mobileprovision`
77-
- Windows: `certutil -encode data.txt tmp.b64`
75+
2. [Create the provisioning profile](code-sign-ios.md#create-an-ios-provisioning-profile) and run this command to encode it to base64:
76+
- Mac: base64 `-i example.mobileprovision`
77+
- Windows: `certutil -encode data.txt tmp.b64`
7878

79-
3. Get the outputted `base64` string from previous step and upload to Keyvault secret. Then, get the .p12 file and upload it to Keyvault Certificate.
79+
3. Get the outputted `base64` string from previous step and upload to Keyvault secret. Then, get the .p12 file and upload it to Keyvault Certificate.
8080

81-
:::image type="content" source="media/wrap-canvas-app/wrap-2.png" alt-text="Create a cert for iOS.":::
81+
:::image type="content" source="media/wrap-canvas-app/wrap-2.png" alt-text="Create a cert for iOS.":::
8282

8383
6. Once iOS or Android certificates are created and uploaded, add three tags with the name as the bundle id, and the value corresponding to the name of the uploaded certificate(s).
8484

0 commit comments

Comments
 (0)