{
  "schema_version": 2,
  "id": "operate/rs/release-notes/legacy-release-notes/rs-5-2-june-2018",
  "title": "Redis Enterprise Software Release Notes 5.2 (June 2018)",
  "url": "https://redis.io/docs/latest/operate/rs/release-notes/legacy-release-notes/rs-5-2-june-2018/",
  "summary": "",
  "tags": [
    "docs",
    "operate",
    "rs"
  ],
  "last_updated": "2026-09-24T14:54:25+01:00",
  "page_type": "content",
  "content_hash": "435d06b65dc5673615e4a926854ad8bc8a1d9ea673d8b865a0c3732bbdf02d97",
  "sections": [
    {
      "id": "overview-1",
      "title": "Overview",
      "role": "overview",
      "text": "Redis Enterprise Software (RS) 5.2 is now available. Key features\ninclude new data types and casual consistency for active-active (also\nknown as the Redis CRDT or CRDB Conflict-free Replicated Database), as\nwell as enhanced security features."
    },
    {
      "id": "overview",
      "title": "Overview",
      "role": "overview",
      "text": "If you are upgrading from a previous version, make sure to review the\nupgrade instructions before beginning the upgrade process. You can\nupgrade to RS 5.2 from RS 4.5 and above. If you have a version older\nthan 4.5, you should first upgrade to version 5.0 (or at least\n4.5)."
    },
    {
      "id": "new-features",
      "title": "New features",
      "role": "content",
      "text": ""
    },
    {
      "id": "activeactive-redis-crdb-supports-sorted-sets-and-lists",
      "title": "Active-Active Redis (CRDB) supports sorted sets and lists",
      "role": "content",
      "text": "RS 5.2 adds active-active Redis (CRDB) support for Sorted Sets and\nLists. Now all major Redis data types are supported with CRDT, so you\ncan use Redis Enterprise in an active-active manner for all your Redis\nuse cases, with seamless conflict resolution. [Click here](https://redis.io/docs/latest/operate/rs/databases/active-active/develop/develop-for-aa)\nfor more information about how to develop applications with\ngeo-replicated CRDBs."
    },
    {
      "id": "causal-consistency-in-activeactive-redis-crdb",
      "title": "Causal consistency in Active-Active Redis (CRDB)",
      "role": "content",
      "text": "casual consistency in active-active Redis (CRDB) guarantees that the\norder of operations on a specific key will be maintained across all CRDB\ninstances. For instance, if operations A and B were applied on the same\nkey, and B was performed after the effect of A was observed by the CRDB\ninstance that initiated B, then all CRDB instances would observe the\neffect of A before observing the effect of B.\n\nThis way, any causal relationship between operations on the same key is\nalso observed and maintained by every replica. Such capability is\nimportant for various applications, e.g. social network status updates\nor chat applications (assuring that the chronology of messages doesn't\nget mixed up). For more information, [click\nhere](https://redis.io/docs/latest/operate/rs/databases/active-active/causal-consistency)."
    },
    {
      "id": "enhanced-security-features",
      "title": "Enhanced security features",
      "role": "content",
      "text": "- **Admin action audit trail**\n\nManagement actions performed with Redis Software are audited in order\nto fulfill two major objectives: (1) make sure that system management tasks\nare appropriately performed and/or monitored by the Administrator(s),\nand (2) facilitate compliance with regulatory standards such as HIPAA,\nSOC2, PCI, etc.\n\nIn order to fulfill both objectives, audit records contain the\nfollowing information: (1) who performed the action, (2) what exactly\nwas the performed action, (3) when the action was performed, and (4)\nwhether  the action succeeded.\n\nTo get the list of audit records/events, one can use the REST API or\nthe Log page in the UI; the Log page displays the system and user events\nregarding alerts, notifications and\nconfigurations.\n\n- **Ability to disable TLS versions**\n\nVersion 5.2 introduces the option to set the minimum TLS version that\ncan be used for encrypting the various flows. You can do so using the\nREST API or the following rladmin commands:\n\n- For the management UI and the REST API:\n\n[code example]\n\n- For the data path encryption:\n\n[code example]\n\nNote that communications that use older TLS versions will not be\nallowed.\n\n- **HTTPS enforcement**\n\nWith this feature, you can restrict REST API  access to only those\nusing HTTPS. In order to do so, use the REST API or the following\nrladmin command:\n\n[code example]"
    },
    {
      "id": "additional-capabilities",
      "title": "Additional capabilities",
      "role": "content",
      "text": "- Support for Redis version 4.0.9\n- Fixes for Redis important security issues related to the Lua\n    scripting engine"
    },
    {
      "id": "information",
      "title": "Information",
      "role": "content",
      "text": "- The end-of-service-life (EOSL) for Redis Enterprise Software 4.4.X\n    is June 30th, 2018, in accordance with our [published\n    policy](https://redis.io/docs/latest/operate/rs/installing-upgrading/product-lifecycle).\n    We recommend that customers running version 4.4 or below\n    upgrade to the latest version."
    },
    {
      "id": "important-fixes",
      "title": "Important fixes",
      "role": "content",
      "text": "- RS19755 - Added the ability to enforce HTTPS communication when\n    accessing REST API\n- RS19571 - Fixed RHEL installation when FIPS mode is\n    enabled\n- RS19490 - Fixed a failure while upgrading from 4.5 to\n    5.0.2\n- RS19475 - Added the ability to disable TLS versions for the\n    control and data paths\n- RS18712 - Fixed a failure in endpoint failover\n\n- RS17208 - Added an option to disable Redis commands via Rest\n    API\n- RS14973 - Updated NGINX.conf template to turn off exposing the\n    server version\n- RS11181 - Set file permissions of log files, redis-conf files, rdb\n    files and their rotations to \"640\""
    },
    {
      "id": "known-limitations",
      "title": "Known limitations",
      "role": "content",
      "text": "- After creating Redis Enterprise CRDBs which \"Require SSL for CRDB\n    communication only,\" one can set definitions via Rest API to\n    activate \"Require SSL for All Communication\" without providing a\n    certificate. In such case, connections to the cluster will be\n    blocked."
    }
  ],
  "examples": [
    {
      "id": "enhanced-security-features-ex0",
      "language": "sh",
      "code": "rladmin> cluster config min_control_TLS_version [version, e.g. 1.2]",
      "section_id": "enhanced-security-features"
    },
    {
      "id": "enhanced-security-features-ex1",
      "language": "sh",
      "code": "rladmin> cluster config min_data_TLS_version [version, e.g. 1.2]",
      "section_id": "enhanced-security-features"
    },
    {
      "id": "enhanced-security-features-ex2",
      "language": "sh",
      "code": "rladmin> cluster config http_support [disabled | enabled]",
      "section_id": "enhanced-security-features"
    }
  ]
}