Skip to content

Commit 8e31b3b

Browse files
authored
Update package-and-publish-high-trust-sharepoint-add-ins.md
1 parent eb97db5 commit 8e31b3b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/sp-add-ins/package-and-publish-high-trust-sharepoint-add-ins.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -84,12 +84,12 @@ Before you can publish the add-in, it has to be registered with the SharePoint f
8484
## Choose a strategy for obtaining, maintaining and deploying certificates for high-trust SharePoint Add-ins
8585
<a name="Certificate"> </a>
8686

87-
When a developer is using **F5** in Visual Studio to develop and debug a high-trust SharePoint Add-in, the developer can use a self-signed certificate, as described in [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins.md). However, when the add-in is *published* , using a self-signed certificate causes the browser to display a warning page before it will open the remote web application's start page. The user has to choose whether to proceed. Figure 3 shows examples of such warnings.
87+
When a developer is using **F5** in Visual Studio to develop and debug a high-trust SharePoint Add-in, the developer can use a self-signed certificate, as described in [Create high-trust SharePoint Add-ins](create-high-trust-sharepoint-add-ins.md). However, when the add-in is *published* , using a self-signed certificate causes the browser to display a warning page before it will open the remote web application's start page. The user has to choose whether to proceed. Figure 2 shows examples of such warnings.
8888

8989

9090

9191

92-
**Figure 3. Warnings for self-signed certificates**
92+
**Figure 2. Warnings for self-signed certificates**
9393

9494

9595

@@ -177,9 +177,9 @@ Skip the next procedure if you are using ISS Manager 8.
177177
3. Double-click the **Server Certificates** icon.
178178

179179

180-
4. In the **Server Certificates** list, right-click the certificate, and then select **Export**, as shown in Figure 4.
180+
4. In the **Server Certificates** list, right-click the certificate, and then select **Export**, as shown in Figure 3.
181181

182-
**Figure 4. Exporting a certificate**
182+
**Figure 3. Exporting a certificate**
183183

184184

185185

0 commit comments

Comments
 (0)