Atomicorp ModSecurity ruleset update fails

Symptoms

• Atomicorp ModSecurity ruleset fails to be updated with the following error in Plesk UI:
  

  PLESK_ERROR: Failed to install the ModSecurity rule set: modsecurity_ctl failed: gpg: key 4520AFA9: "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 gpg: Signature made Wed May 24 19:53:48 2017 +08 using RSA key ID 4520AFA9 gpg: Good signature from "Atomicorp (Atomicorp Official Signing Key) <support@atomicorp.com>" gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 1818 66DF 9DAC A40E 5B42 9B08 FFBD 5D0A 4520 AFA9 TERM environment variable not set. aum failed with exitcode 3. stdout: Checking versions ... ASL version is current: package asl is not installed[75G[[1;31m[1;32mPASS[0m[0m] Authorization failed attempting to download an update. The username or password may be invalid, or your license may be expired. Please log in to the License Manager at https://www.atomicorp.com/amember/member.php and verify your account. Further information may be found at: https://www.atomicorp.com/wiki/index.php/ASL_FAQ#HTTP_Error_401:_Authorization_Required. ------------------------------------------------------------------------------- Errors were encountered: L CODE SOURCE MESSAGE - ---- ----------------------------- ------------------------------------------ [1;31m3 303 Core::distributed_update Invalid user credentials [0m103.226.172.94 stderr: Unable to download tortix rule set

• Using login-password pair provided in /etc/aps/config at https://www.atomicorp.com/amember/member.php shows that it is incorrect.

Cause

An account has not been activated properly on the Atomicorp site.

Resolution

Contact Atomicorp team for activating the account.