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/service-connector/how-to-integrate-redis-cache.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.date: 02/02/2024
10
10
11
11
# Integrate Azure Cache for Redis with Service Connector
12
12
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. (Note that you might still be able to connect to Azure Cache for Redis in other programming languages without using Service Connector.)
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. (You might still be able to connect to Azure Cache for Redis in other programming languages without using Service Connector.)
14
14
15
15
## Supported compute services
16
16
@@ -24,7 +24,7 @@ You can use Service Connector to connect the following compute services to Azure
24
24
25
25
## Supported authentication and client types
26
26
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, while "No" means that it isn't 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,11 +36,11 @@ The following table shows which combinations of authentication methods and clien
36
36
| Python | Yes | Yes | Yes | Yes |
37
37
| None | Yes | Yes | Yes | Yes |
38
38
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 using Service Connector. The only supported authentication methods for Go and Java - Spring Boot are secret / connection string or service principal.
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 following environment variable names and application properties to connect compute services to your Redis server. For each example, replace the placeholders `<redis-server-name>`, and `<redis-key>` with your own Redis server name and key. Check the [Service Connector internals](concept-service-connector-internals.md#configuration-naming-convention) article to learn more about naming conventions.
43
+
Use the following environment variable names and application properties to connect compute services to your Redis server. For each example, replace the placeholders `<redis-server-name>` and `<redis-key>` with your own Redis server name and key. 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
@@ -68,13 +68,13 @@ The following steps and code show you how to use a user-assigned managed identit
68
68
### Connection string
69
69
70
70
> [!WARNING]
71
-
> 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 only use this flow when more secure flows, such as managed identities, aren't viable.
71
+
> 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
72
73
73
#### [.NET](#tab/dotnet)
74
74
75
75
| Default environment variable name | Description | Example value |
0 commit comments