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
@@ -16,7 +16,7 @@ Azure Cache for Redis is based on the Redis open-source, in-memory data store. R
16
16
17
17
Each client library has its own API that calls Redis servers using Redis commands. The client libraries are built to communicate with any Redis server.
18
18
19
-
Each client maintains reference documentation for its own library, and provides links to get support through the client library developer community. Microsoft and the Azure Redis team don't own the development or support for any client libraries.
19
+
Clients maintain reference documentation for their own libraries, and provides links to get support through the client library developer community. Microsoft and the Azure Redis team don't own the development or support for any client libraries.
20
20
21
21
Microsoft and Azure Redis do recommend some libraries, based on popularity and whether there's an active online support community to answer questions. These libraries are under active development and often release new versions with reliability and performance improvements. Microsoft recommends using the latest available version, and upgrading regularly as new versions become available.
22
22
@@ -60,7 +60,7 @@ Besides the reference documentation, you can use the following tutorials to get
60
60
61
61
## Best practices for Redisson (Java)
62
62
63
-
Here are some recommended best practices for the Redisson client library:
63
+
Here are some recommended best practices for the [Redisson](https://redisson.pro/) client library:
64
64
65
65
- Use Redisson 3.14.1 or higher. Older versions contain known connection leak issues that cause problems after failovers.
66
66
@@ -74,7 +74,7 @@ Here are some recommended best practices for the Redisson client library:
74
74
75
75
- Reset the idle connection timeout if necessary. Redisson has a default 10-second idle connection timeout, which can lead to more closing and reopening of connections than ideal.
76
76
77
-
-For an article about Redisson support for Java EE JCache as the store for HTTP session state in IBM Liberty on an Azure Kubernetes Service (AKS) cluster, see [Using Azure Redis as session cache for WebSphere Liberty or Open Liberty](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache).
77
+
-See [Using Azure Redis as session cache for WebSphere Liberty or Open Liberty](/azure/developer/java/ee/how-to-deploy-java-liberty-jcache) for information about using Redisson with Java EE JCache to store HTTP session state on an Azure Kubernetes Service (AKS) cluster in IBM Libery.
78
78
79
79
- Use the following recommended baseline configuration for cluster mode, and modify it as needed.
For other considerations about using Azure Redis with other clouds, see the following links:
40
+
The Azure Redis Enterprise and Enterprise Flash tiers are available only in the Public cloud.
41
+
42
+
For more considerations about using Azure Redis with other clouds, see the following links:
41
43
42
44
- [Azure Government Databases](/azure/azure-government/compare-azure-government-global-azure)
43
45
- [Azure operated by 21Vianet Cloud](https://www.azure.cn/home/features/redis-cache/)
44
46
45
47
For information about using Azure Redis with PowerShell in Azure Government Cloud and Azure operated by 21Vianet Cloud, see [How to connect to other clouds - PowerShell](../redis/how-to-manage-redis-cache-powershell.md#how-to-connect-to-other-clouds).
46
48
47
-
The Azure Redis Enterprise and Enterprise Flash tiers are available only in the Public cloud.
48
-
49
-
- question: |
50
-
What region should I locate my cache in?
51
-
answer: |
52
-
For best performance and lowest latency, locate your Azure Redis cache in the same Azure region as your cache client application.
53
-
54
49
- question: |
55
50
Where does my cached data reside?
56
51
answer: |
@@ -65,6 +60,11 @@ sections:
65
60
66
61
You need to explicitly configure Azure Redis to use the preceding features. You also have complete control over the region where the storage account or secondary cache is located.
67
62
63
+
- question: |
64
+
Which region should I locate my cache in?
65
+
answer: |
66
+
For best performance and lowest latency, locate your Azure Redis cache in the same Azure region as your cache client application.
Copy file name to clipboardExpand all lines: articles/azure-cache-for-redis/cache-tls-configuration.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,15 +7,17 @@ description: Learn about the TLS protocol configuration and how to use TLS to se
7
7
ms.topic: overview
8
8
ms.custom:
9
9
- ignite-2024
10
-
ms.date: 01/23/2024
10
+
ms.date: 05/05/2025
11
11
appliesto:
12
12
- ✅ Azure Cache for Redis
13
13
# Customer intent: As a developer creating a service that uses a cache, I want to know the details about TLS connections so that I know my service is secure.
14
14
---
15
15
16
16
# Azure Cache for Redis TLS protocol configuration settings
17
17
18
-
Transport Layer Security (TLS) is a cryptographic protocol that provides secure communication over a network. Azure Cache for Redis supports TLS on all tiers. When you create a service that uses an Azure Redis cache, it's best to connect using TLS.
18
+
Transport Layer Security (TLS) is a cryptographic protocol that provides secure communication over a network. Azure Cache for Redis supports TLS on all tiers, and requires TLS encrypted communications by default. Using TLS is recommended as a best practice across virtually all Azure Redis use cases.
19
+
20
+
The option to connect Azure Redis without TLS is included for backwards compatibility purposes. If your client library or tool doesn't support TLS, you can enable unencrypted connections through the [Azure portal](cache-configure.md#access-ports) or [management APIs](/rest/api/redis/redis/update). This article describes how to enable non-TLS access by using the Azure portal.
19
21
20
22
> [!IMPORTANT]
21
23
> TLS 1.0 and 1.1 are no longer supported. For more information, see [Remove TLS 1.0 and 1.1 from use with Azure Cache for Redis](cache-remove-tls-10-11.md),
@@ -42,6 +44,10 @@ The TLS 1.3 cipher suites are as follows:
42
44
43
45
## How to enable or disable TLS
44
46
47
+
Azure Cache for Redis
48
+
49
+
50
+
45
51
Enabling and disabling TLS is different for different Azure Redis tiers.
0 commit comments