edit-icon download-icon

Password-free access

Last Updated: Dec 14, 2017

Background

Generally, SASL authentication is performed on accesses to an ApsaraDB for Memcache instance. That is, you must enter the correct user name and password to perform operations on the data. Some users also hope ApsaraDB for Memcache supports password-free access to facilitate usage and integration of third-party software, which is actually already supported by ApsaraDB for Memcache. You can enable password-free access after setting the whitelist so that all applications on the whitelist can access the corresponding ApsaraDB for Memcache instance without a password.

Notes:

  • The ECS instance and Memcache instance you want to enable password-free access must be in the same region.

  • If an application needs to access multiple ApsaraDB for Memcache instances on the same ECS server, you can bind an IP address with multiple Memcache instances to allow password-free access.

  • Memcache text protocol does not support password access. If you use the text protocol to access Memcache, you must enable IP whitelist password-free access.

  • Before enabling whitelist password-free access, you must remove 0.0.0.0/0 from the whitelist, or the password-free access function will not be able to take effect.

Procedure

  1. Log on to the Memcache console.

  2. On the Instance List page, locate the target instance.

  3. Click Instance ID or Manage at the right side to go to the Instance Information page.

  4. Select Security Settings on the left-side navigation pane.

  5. After setting IP whitelist, select the Enable option next to Password-free Access and click Submit, then you can access the current Memcache instance without a password.

  • The password-free access function does not take effect after being enabled.

    For the sake of security, Memcache disables the whitelist password-free access function when 0.0.0.0/0 is on the whitelist. Check if the 0.0.0.0/0 IP segment is on the whitelist. If yes, remove it from the whitelist group.

  • The password-free access function becomes invalid after upgrading to a new version. For the sake of security, the new version disables the whitelist password-free access function when 0.0.0.0/0 is on the whitelist, while the earlier version does not have this setting. Therefore, if you have upgraded to a new version, check if the 0.0.0.0/0 IP segment is on the whitelist. If yes, remove it from the whitelist group.

Thank you! We've received your feedback.