You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You need to have [Azure Key Vault](/azure/key-vault/general/basic-concepts) set up to automatically sign your Android or iOS mobile app package in **Step 2** of wrap wizard. Azure key vault is a cloud service that provides a secure store for secrets. You can securely store keys, passwords, certificates, and other secrets. More information: [Intoduction to Azure key vault](/azure/key-vault/general/overview).
17
+
You need to have [Azure Key Vault](/azure/key-vault/general/basic-concepts) set up to automatically sign your Android or iOS mobile app package in [Step 2](wrap-how-to.mdstep-2-target-platform) of wrap wizard. Azure key vault is a cloud service that provides a secure store for secrets. You can securely store keys, passwords, certificates, and other secrets. More information: [Intoduction to Azure key vault](/azure/key-vault/general/overview).
18
18
19
19
You can use an exsiting Azure key vault or create a new one one [Azure portal](https://portal.azure.com) using the instructions below.
20
20
21
-
**Prerequisites**
21
+
## Prerequisites
22
22
23
23
- Azure Active Directory subscription to [create Key Vault](/azure/key-vault/general/quick-create-portal).
24
24
- Admin access for your tenant.
@@ -33,33 +33,34 @@ Follow these steps to create **Azure key vault** for wrap for Power Apps and con
33
33
34
34
2. In your default subscription's **Access Control (IAM)**, add a **Reader** role assignment to the **Service Principal** representing your app, e.g. **Wrap KeyVault Access App**. Make sure it is present in the **Subscription's IAM**, and the **Keyvault's IAM**.
35
35
36
-
Go to **Access control (IAM)** tab and select **Add role assignment** option under **Add** menu button.
36
+
1.Go to **Access control (IAM)** tab and select **Add role assignment** option under **Add** menu button.
37
37
38
-
> [!div class="mx-imgBorder"]
39
-
> 
38
+
> [!div class="mx-imgBorder"]
39
+
> 
40
40
41
-
Select **Job fucntion roles** tab and make sure **Reader** role is selcetdd. Then click on **Members** tab in the top menu.
41
+
2.Select **Job fucntion roles** tab and make sure **Reader** role is selcetdd. Then click on **Members** tab in the top menu.
42
42
43
-
> [!div class="mx-imgBorder"]
44
-
>
43
+
> [!div class="mx-imgBorder"]
44
+

45
45
46
-
Search for **Wrap KeyVault Access App** on **Members** tab.
46
+
3.Search for **Wrap KeyVault Access App** on **Members** tab.
47
47
48
-
> [!div class="mx-imgBorder"]
49
-
> 
48
+
> [!div class="mx-imgBorder"]
49
+
> 
50
50
51
-
Select **Wrap KeyVault Access App** and click on **Review + assign** button on the bottom of the tab to assign **Reader** role to it.
51
+
4.Select **Wrap KeyVault Access App** and click on **Review + assign** button on the bottom of the tab to assign **Reader** role to it.
52
52
53
-
> [!div class="mx-imgBorder"]
54
-
> 
55
-
56
-
4. Create or access existing key vault. Please ensure this key vault is located in the default subscription for your tenant. More information: [Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal).
53
+
> [!div class="mx-imgBorder"]
54
+
> 
55
+
56
+
57
+
3. Create or access existing key vault. Please ensure this key vault is located in the default subscription for your tenant. More information: [Create a key vault using the Azure portal](/azure/key-vault/general/quick-create-portal).
57
58
58
-
5. Add access policies for the key vault.
59
+
4. Add access policies for the key vault.
59
60
60
61
:::image type="content" source="media/wrap-canvas-app/wrap-keyvault.gif" alt-text="Add access policies for the key vault.":::
61
62
62
-
6. Follow one of the these options, depending on your device:
63
+
5. Follow one of the these options, depending on your device:
63
64
- For Android, create the .pfx file upload it to the keyvault certificate section. More information: [Generate keys](code-sign-android.md#generate-keys)
64
65
65
66
:::image type="content" source="media/wrap-canvas-app/wrap-1.png" alt-text="Create a cert for Android.":::
@@ -78,172 +79,11 @@ Follow these steps to create **Azure key vault** for wrap for Power Apps and con
78
79
79
80
:::image type="content" source="media/wrap-canvas-app/wrap-2.png" alt-text="Create a cert for iOS.":::
80
81
81
-
7. 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).
82
+
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).
- In your Default subscription's **Access Control (IAM)** on Azure portal at [https://portal.azure.com](https://portal.azure.com), add a **Reader** role assignment to the **Service Principal** representing your app, e.g. **Wrap KeyVault Access App**. Make sure it is present in both **Subscription's IAM**, and the **Keyvault's IAM**.
102
-
103
-
Go to **Access control (IAM)** tab and select **Add role assignment** option under **Add** menu button.
104
-
105
-
> [!div class="mx-imgBorder"]
106
-
> 
107
-
108
-
Select **Job fucntion roles** tab and make sure **Reader** role is selcetdd. Then click on **Members** tab in the top menu.
109
-
110
-
> [!div class="mx-imgBorder"]
111
-
> 
112
-
113
-
Search for **Wrap KeyVault Access App** on **Members** tab.
114
-
115
-
> [!div class="mx-imgBorder"]
116
-
> 
117
-
118
-
Select **Wrap KeyVault Access App** and click on **Review + assign** button on the bottom of the tab to assign **Reader** role to it.
119
-
120
-
> [!div class="mx-imgBorder"]
121
-
> 
122
-
123
-
124
-
### Error code 1000119
125
-
126
-
| Error code | Description |
127
-
| ------------- |:-------------:|
128
-
|1000119 | Keyvault does not exist, or Keyvault is missing access privileges|
129
-
130
-
- Verify that your Azure key vault is in the Default Subscription for your tenant.
131
-
132
-
- Make sure to to select **Vault access policy** option when creating your key vault.
- In your Default subscription's **Access Control (IAM)** on Azure portal at [https://portal.azure.com](https://portal.azure.com), add a **Reader** role assignment to the **Service Principal** representing your app, e.g. **Wrap KeyVault Access App**. Make sure it is present in both **Subscription's IAM**, and the **Keyvault's IAM**.
142
-
143
-
Go to **Access control (IAM)** tab and select **Add role assignment** option under **Add** menu button.
144
-
145
-
> [!div class="mx-imgBorder"]
146
-
> 
147
-
148
-
Select **Job fucntion roles** tab and make sure **Reader** role is selcetdd. Then click on **Members** tab in the top menu.
149
-
150
-
> [!div class="mx-imgBorder"]
151
-
> 
152
86
153
-
Search for **Wrap KeyVault Access App** on **Members** tab.
154
-
155
-
> [!div class="mx-imgBorder"]
156
-
> 
157
-
158
-
Select **Wrap KeyVault Access App** and click on **Review + assign** button on the bottom of the tab to assign **Reader** role to it.
159
-
160
-
> [!div class="mx-imgBorder"]
161
-
> 
> 
170
-
171
-
### Error code 1000120
172
-
173
-
| Error code | Description |
174
-
| ------------- |:-------------:|
175
-
|1000120 | No organization ID tags found on key vault|
176
-
177
-
- Go to [Power Platform admin center](https://admin.powerplatform.microsoft.com/environments) and click on the **Environment** where your wrap project is.
- In your keyvault at [Azure portal](https://portal.azure.com), go to **Tags** and add a new tag named **organization-id** and add your **Organization ID** from previous step as a value for this tag.
> 
204
-
205
-
206
-
- Add a new **Tag** for your **Android Certificate**.
207
-
1. The **Tag name** should be based on the **bundle id** that you used in your **wrap project**. For example, if the **bundle id** for your wrapped app is **com.testApp.wrap**, then the new **Tag name** should be **com.testApp.wrap.keystore**.
208
-
2. The **Tag value** should correspod to the name you chose for your **Certificate** when uploading a certificate file in the previous step. For example, if your **Cerfificate** is named **AndroidWrapCertificate**, then the value for the **Tag value** should also be **AndroidWrapCertificate**.
209
-
210
-
> [!div class="mx-imgBorder"]
211
-
> 
> 
226
-
227
-
- Add a new **Tag** for your **iOS Certificate**.
228
-
1. The **Tag name** should be based on the **bundle id** that you used in your **wrap project**. For example, if the **bundle id** for your wrapped app is **com.testApp.wrap**, then the new **Tag name** should be **com.testApp.wrap.cert**.
229
-
2. The **Tag value** should correspod to the name you chose for your **Certificate** when uploading a certificate file in the previous step. For example, if your **Cerfificate** is named **iOSCertificate1**, then the value for the **Tag value** should also be **iOSCertificate1**.
230
-
231
-
> [!div class="mx-imgBorder"]
232
-
> 
233
-
234
-
### Error code 1000123
235
-
236
-
| Error code | Description |
237
-
| ------------- |:-------------:|
238
-
|1000123 | iOS profile is not valid|
239
-
240
-
- Import your **Provisioning Profile** as a **Secret**
241
-
- Add a new **Tag** for your **Provisioning Profile**.
242
-
-1. The **Tag name** should be based on the **bundle id** that you used in your **wrap project**. For example, if the **bundle id** for your wrapped app is **com.testApp.wrap**, then the new **Tag name** should be **com.testApp.wrap.profile**.
243
-
2. The **Tag value** should correspod to the name you chose for your **Secret** when uploading a povisioning profile in the previous step. For example, if your **Secret** is named **iOSProvisioningProfileSecret**, then the value for the **Tag value** should also be **iOSProvisioningProfileSecret**.
244
-
245
-
> [!div class="mx-imgBorder"]
246
-
> 
0 commit comments