Skip to content

Commit e03f26b

Browse files
cephalin feedback
1 parent 89b7b1a commit e03f26b

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/app-service/tutorial-java-tomcat-mysql-app.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -180,15 +180,15 @@ The creation wizard generated the database connectivity string for you already a
180180
1. Select **AZURE_MYSQL_CONNECTIONSTRING**. It contains a JDBC connection string. If you add an app setting that contains a valid Oracle, SQL Server, PostgreSQL, or MySQL connection string, App Service injects it as a Java Naming and Directory Interface (JNDI) data source in the Tomcat server's *context.xml* file.
181181
1. In **Add/Edit application setting**, in the **Value** field, find the *password=* part at the end of the string.
182182
1. Copy the password string after *Password=* for use later.
183-
This app setting lets you connect to the MySQL database secured behind a private endpoint. However, the secret is saved directly in the App Service app, which isn't the best. You change this.
183+
This app setting lets you connect to the MySQL database secured behind a private endpoint. However, the secret is saved directly in the App Service app, which isn't the best. You'll change this.
184184
:::column-end:::
185185
:::column:::
186186
:::image type="content" source="./media/tutorial-java-tomcat-mysql-app/azure-portal-secure-connection-secrets-1.png" alt-text="A screenshot showing how to see the value of an app setting." lightbox="./media/tutorial-java-tomcat-mysql-app/azure-portal-secure-connection-secrets-1.png":::
187187
:::column-end:::
188188
:::row-end:::
189189
:::row:::
190190
:::column span="2":::
191-
**Step 2: Create a Key Vault for secure management of secrets**
191+
**Step 2: Create a key vault for secure management of secrets**
192192
1. In the top search bar, type "*key vault*", then select **Marketplace** > **Key Vault**.
193193
1. In **Resource Group**, select **msdocs-tomcat-mysql-tutorial**.
194194
1. In **Key vault name**, type a name that consists of only letters and numbers.
@@ -200,12 +200,12 @@ The creation wizard generated the database connectivity string for you already a
200200
:::row-end:::
201201
:::row:::
202202
:::column span="2":::
203-
**Step 3: Secure the Key Vault with a Private Endpoint**
203+
**Step 3: Secure the key vault with a Private Endpoint**
204204
1. Select the **Networking** tab.
205205
1. Unselect **Enable public access**.
206206
1. Select **Create a private endpoint**.
207207
1. In **Resource Group**, select **msdocs-tomcat-mysql-tutorial**.
208-
1. In **Name**, type a name for the Private Endpoint that consists of only letters and numbers.
208+
1. In **Name**, type a name for the private endpoint that consists of only letters and numbers.
209209
1. In **Region**, set it to the same location as the resource group.
210210
1. In the dialog, in **Location**, select the same location as your App Service app.
211211
1. In **Resource Group**, select **msdocs-tomcat-mysql-tutorial**.
@@ -261,15 +261,15 @@ The creation wizard generated the database connectivity string for you already a
261261
:::row:::
262262
:::column span="2":::
263263
**Step 7: Verify the Key Vault integration**
264-
1. From the left menu, select **Environment variables > Connection strings** again.
264+
1. From the left menu, select **Settings > Environment variables** again.
265265
1. Next to **AZURE_MYSQL_CONNECTIONSTRING**, select **Show value**. The value should be `@Microsoft.KeyVault(...)`, which means that it's a [key vault reference](app-service-key-vault-references.md) because the secret is now managed in the key vault.
266266
:::column-end:::
267267
:::column:::
268268
:::image type="content" source="./media/tutorial-java-tomcat-mysql-app/azure-portal-secure-connection-secrets-7.png" alt-text="A screenshot showing how to see the value of the MySQL environment variable in Azure." lightbox="./media/tutorial-java-tomcat-mysql-app/azure-portal-secure-connection-secrets-7.png":::
269269
:::column-end:::
270270
:::row-end:::
271271

272-
To summarize, the process involved retrieving the MySQL connection string from the App Service's environment variables, creating an Azure Key Vault for secure secret management with private access, and updating the service connector to store the password in the Key Vault. A secure connection between the App Service and Key Vault was established using a system-assigned managed identity, and the setup was verified by confirming the connection string referenced the Key Vault.
272+
To summarize, the process involved retrieving the MySQL connection string from the App Service's environment variables, creating an Azure Key Vault for secure secret management with private access, and updating the service connector to store the password in the key vault. A secure connection between the App Service app and key vault was established using a system-assigned managed identity, and the setup was verified by confirming the connection string uses a Key Vault reference.
273273

274274
Having issues? Check the [Troubleshooting section](#troubleshooting).
275275

0 commit comments

Comments
 (0)