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
title: Integrate Azure Cache for Redis and Azure Cache Redis Enterprise with Service Connector
3
-
description: Integrate Azure Cache for Redis and Azure Cache Redis Enterprise into your application with Service Connector
2
+
title: Integrate Azure Cache for Redis with Service Connector
3
+
description: Learn how to integrate Azure Cache for Redis and Azure Cache for Redis Enterprise into your application with Service Connector.
4
4
author: maud-lv
5
5
ms.author: malev
6
6
ms.service: service-connector
@@ -10,21 +10,21 @@ ms.date: 02/02/2024
10
10
11
11
# Integrate Azure Cache for Redis with Service Connector
12
12
13
-
This page shows supported authentication methods and clients, and shows sample code you can use to connect Azure Cache for Redis to other cloud services using Service Connector. You might still be able to connect to Azure Cache for Redis in other programming languages without using Service Connector. This page also shows default environment variable names and values (or Spring Boot configuration) you get when you create the service connection.
13
+
You can connect Azure Cache for Redis to other cloud services by using Service Connector. This article outlines supported authentication methods and clients, and provides sample code. It also reveals default environment variable names and values (or Spring Boot configuration) you get when you create the service connection.
14
14
15
15
## Supported compute services
16
16
17
-
Service Connector can be used to connect the following compute services to Azure Cache for Redis:
17
+
You can use Service Connector to connect the following compute services to Azure Cache for Redis:
18
18
19
19
- Azure App Service
20
20
- Azure Container Apps
21
21
- Azure Functions
22
22
- Azure Kubernetes Service (AKS)
23
23
- Azure Spring Apps
24
24
25
-
## Supported Authentication types and client types
25
+
## Supported authentication and client types
26
26
27
-
The table below shows which combinations of authentication methods and clients are supported for connecting your compute service to Azure Cache for Redis using Service Connector. A “Yes” indicates that the combination is supported, while a “No” indicates that it is not supported.
27
+
The following table shows which combinations of authentication methods and clients are supported for connecting your compute service to Azure Cache for Redis by using Service Connector. "Yes" means that the combination is supported. "No" means that it isn't supported.
28
28
29
29
| Client type | System-assigned managed identity | User-assigned managed identity | Secret / connection string | Service principal |
@@ -36,114 +36,115 @@ The table below shows which combinations of authentication methods and clients a
36
36
| Python | Yes | Yes | Yes | Yes |
37
37
| None | Yes | Yes | Yes | Yes |
38
38
39
-
This table indicates that the only supported authentication method for all client types in the table is the Secret / connection string method. Other authentication methods are not supported for any of the client types to connect to Azure Cache for Redis using Service Connector.
39
+
All client types, except for Go and Java - Spring Boot, can use any of the authentication methods referenced in the table to connect to Azure Cache for Redis by using Service Connector. The only supported authentication methods for Go and Java - Spring Boot are secret / connection string or service principal.
40
40
41
41
## Default environment variable names or application properties and sample code
42
42
43
-
Use the environment variable names and application properties listed below to connect compute services to Redis Server. For each example below, replace the placeholder texts `<redis-server-name>`, and `<redis-key>` with your own Redis server name and key. For more information about naming conventions, check the [Service Connector internals](concept-service-connector-internals.md#configuration-naming-convention) article.
43
+
Use the following environment variable names and application properties to connect compute services to your Redis server. To learn more about naming conventions, check the [Service Connector internals](concept-service-connector-internals.md#configuration-naming-convention) article.
44
44
45
45
### System-assigned managed identity
46
46
47
47
| Default environment variable name | Description | Sample value |
|`AZURE_REDIS_CLIENTID`|Managed-identity client ID |`<client-ID>`|
62
63
63
64
#### Sample code
64
65
65
-
Refer to the steps and code below to connect to Redis using a user-assigned managed identity.
66
+
The following steps and code show you how to use a user-assigned managed identity to connect to Redis.
67
+
66
68
[!INCLUDE [code sample for Redis](./includes/code-redis-me-id.md)]
67
69
68
-
### Connection String
70
+
### Connection string
69
71
70
72
> [!WARNING]
71
-
> Microsoft recommends that you use the most secure authentication flow available. The authentication flow described in this procedure requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows, such as managed identities, aren't viable.
73
+
> We recommend that you use the most secure authentication flow available. The authentication flow described here requires a very high degree of trust in the application, and carries risks that aren't present in other flows. You should use this flow only when more secure flows, such as managed identities, aren't viable.
72
74
73
-
#### [.NET](#tab/dotnet)
75
+
#### [.NET](#tab/dotnet)
74
76
75
77
| Default environment variable name | Description | Example value |
0 commit comments