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
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-azure-active-directory-for-authentication.md
+6-10Lines changed: 6 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ author: flang-msft
7
7
ms.custom: references_regions
8
8
ms.service: cache
9
9
ms.topic: conceptual
10
-
ms.date: 01/29/2024
10
+
ms.date: 02/07/2024
11
11
ms.author: franlanglois
12
12
13
13
---
@@ -43,15 +43,13 @@ To use the ACL integration, your client application must assume the identity of
43
43
44
44
## Enable Microsoft Entra ID authentication on your cache
45
45
46
-
If you would like to use a custom access policy instead of Redis Data Owner, go to the **Data Access Configuration** on the Resource menu. For more information, see [Configure a custom data access policy for your application](cache-configure-role-based-access-control.md#configure-a-custom-data-access-policy-for-your-application).
47
-
48
46
1. In the Azure portal, select the Azure Cache for Redis instance where you'd like to configure Microsoft Entra token-based authentication.
49
47
50
48
1. Select **Authentication** from the Resource menu.
51
49
52
50
1. In the working pane, select **(PREVIEW) Enable Microsoft Entra Authorization**.
53
51
54
-
1. Select **Enable Microsoft Entra Authorization**, and enter the name of a valid user. Then, select **Save**. You could also enter a managed identity or service principal to connect to your cache instance.
52
+
1. Select **Enable Microsoft Entra Authorization**, and enter the name of a valid user. The user you enter is automatically assigned _Data Owner Access Policy_ by default when you select **Save**. You can also enter a managed identity or service principal to connect to your cache instance.
55
53
56
54
:::image type="content" source="media/cache-azure-active-directory-for-authentication/cache-enable-microsoft-entra.png" alt-text="Screenshot showing authentication selected in the resource menu and the enable Microsoft Entra authentication checked.":::
57
55
@@ -96,15 +94,13 @@ Because most Azure Cache for Redis clients assume that a password and access key
96
94
97
95
1. Update your Redis connection logic to use following `UserName` and `Password`:
98
96
99
-
-`UserName` = Object ID of your managed identity or service principal
100
-
101
-
-`Password` = Microsoft Entra token that you acquired using MSAL
97
+
`UserName` = Object ID of your managed identity or service principal
98
+
`Password` = Microsoft Entra token that you acquired using MSAL
102
99
103
100
1. Ensure that your client executes a Redis [AUTH command](https://redis.io/commands/auth/) automatically before your Microsoft Entra token expires using:
104
101
105
-
-`UserName` = Object ID of your managed identity or service principal
106
-
107
-
-`Password` = Microsoft Entra token refreshed periodically
102
+
`UserName` = Object ID of your managed identity or service principal
103
+
`Password` = Microsoft Entra token refreshed periodically
0 commit comments