Skip to content

Commit b1b8998

Browse files
Merge pull request #49793 from KarlErickson/karler-ropc
ROPC fixes
2 parents d501380 + e47e747 commit b1b8998

File tree

3 files changed

+11
-2
lines changed

3 files changed

+11
-2
lines changed

learn-pr/advocates/deploy-java-ee-app-to-jboss-app-service/includes/3-exercise-deploy-azure-database-mysql.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,8 @@ export MYSQL_USER=<MySQL-admin-user-name>
100100
export MYSQL_PASSWORD=<MySQL-password>
101101
```
102102

103+
[!INCLUDE [security-note](../../../includes/security-note.md)]
104+
103105
## Get data from the sample database
104106

105107
In this module, you use a sample database called `world` from the official MySQL website. To get the data, use the following steps:

learn-pr/azure/deploy-java-quarkus-azure-container-app-postgres/includes/5-exercise-rg-postgres.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -94,8 +94,7 @@ echo "POSTGRES_CONNECTION_STRING_SSL=$POSTGRES_CONNECTION_STRING_SSL"
9494

9595
Note the connection string that's returned.
9696

97-
> [!NOTE]
98-
> Microsoft recommends using the most secure authentication flow available. The authentication flow described in this procedure, such as for databases, caches, messaging or AI services, requires a very high degree of trust in the application and carries risks not present in other flows. Use this flow only when more secure options, like managed identities for passwordless or keyless connections, are not viable. For local machine operations, prefer user identities for passwordless or keyless connections.
97+
[!INCLUDE [security-note](../../../includes/security-note.md)]
9998

10099
## Configure the Quarkus application to connect to the PostgreSQL database
101100

learn-pr/includes/security-note.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
---
2+
author: KarlErickson
3+
ms.author: karler
4+
ms.date: 03/31/2025
5+
---
6+
7+
> [!NOTE]
8+
> Microsoft recommends using the most secure authentication flow available. The authentication flow described in this procedure, such as for databases, caches, messaging, or AI services, requires a high degree of trust in the application and carries risks not present in other flows. Use this flow only when more secure options, like managed identities for passwordless or keyless connections, aren't viable. For local machine operations, prefer user identities for passwordless or keyless connections.

0 commit comments

Comments
 (0)