Magento Open Source, 2.0.x

Magento 2.0.18 is the final 2.0.x release. After March 2018, Magento 2.0.x will no longer receive security patches, quality fixes, or documentation updates. To maintain your site's performance, security, and PCIPayment Card Industry: Refers to debit and credit cards and their associated businesses. compliance, upgrade to the latest version of Magento.

Configuring Admin Security

Magento recommends that you take a multifaceted approach to protect the security of your store. You can begin by using a custom Admin URL that is not easy to ascertain, rather than the obvious “AdminThe password-protected back office of your store where orders, catalog, content, and configurations are managed.” or “Backend.” .As a best practice, use only strong Admin passwords that include a combination of letters, numbers, and symbols. For increased security, consider implementing two-factor authentication that generates a token on a separate device. To learn more, see the selection of security-related extensions on Magento Marketplace.

The Admin security configuration gives you the ability to add a secret key to URLs, require passwords to be case sensitive, and to limit the length of Admin sessions, the lifetime of passwords, and the number of loginThe process of signing into an online account. attempts that can be made before the Admin user account is locked. For increased security, you can configure the length of keyboard inactivity before the current session expires, and require the user name and password to be case-sensitive. For additional security, the Admin login can be configured to require a CAPTCHA.


To configure Admin security:

1. On the Admin sidebarThe right or left column of a two-column page layout., tap Stores. Then under Settings, choose Configuration.
2. In the panel on the left under Advanced, choose Admin.
3. Expand the Security section. Then, do the following:
a. To append a secret key to the Admin URLUniform Resource Locator: The unique address of a page on the internet. as a precaution against exploits, set Add Secret Key to URLs to “Yes.” This setting is enabled by default.
b. To require that the use of upper- and lowercase characters in any login credentials entered match what is stored in the system, set Login is Case Sensitive to “Yes.”
c. To determine the length of an Admin session before it times out, enter the duration of the session in seconds, in the Admin Session Lifetime (seconds) field. The value must be 60 seconds or greater.
d. In the Maximum Login Failures to Lockout Account field, enter the number of times a user can try to log in to the Admin before the account is locked. By default, six attempts are allowed . Leave the field empty for unlimited login attempts.
e. In the Lockout Time (minutes) field, enter the number of minutes that an Admin account is locked when the maximum number of attempts is met.
f. To limit the lifetime of Admin passwords, enter the number of days a password is valid in the Password Lifetime (days) field. /For an unlimited lifetime, leave the field blank.
g. Set Password Change to one of the following:
  • Forced

    Requires that Admin users change their passwords after the account is set up.


    Recommends that Admin users change their passwords after account is set up.

4. When complete, tap Save Config.