Skip to content

Commit 327c440

Browse files
committed
add a note to explain microsoft entra authentication is not adopted because aro doesn't support workload identity yet
Signed-off-by: Jianguo Ma <[email protected]>
1 parent 1de12bd commit 327c440

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/openshift/howto-deploy-java-liberty-app.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -216,6 +216,9 @@ The following steps guide you through creating an Azure SQL Database single data
216216
export DB_RESOURCE_GROUP_NAME=<db-resource-group>
217217
```
218218

219+
> [!NOTE]
220+
> This article guides you to create an Azure SQL Database single database with SQL authentication. A more secure practice is to use [Microsoft Entra authentication for Azure SQL](/azure/azure-sql/database/authentication-aad-overview?preserve-view=true&view=azuresql-db) for authenticating the database server connection. Azure Red Hat OpenShift doesn't currently support [Microsoft Entra Workload ID](/entra/workload-id/workload-identities-overview), so SQL authentication is the only available option.
221+
219222
Now that you created the database and Azure Red Hat OpenShift cluster, you can prepare the Azure Red Hat OpenShift cluster to host your WebSphere Liberty application.
220223

221224
## Configure and deploy the sample application

0 commit comments

Comments
 (0)