When installing the package from the Amasty Composer repository for the first time, the system requests the login (Public Key) and password (Private Key). These access keys can be found in the customer account under License Registration tabinside your project (if you haven't created one yet, please do so following the instructions from the hint block on the License Registration page). Click on View link next to your project in the My Production Projects section, and you'll see the keys that are generated automatically after product creation:
A page with project details and composer keys will appear:
Additionally, check out our video guide on how to create composer keys:
If you didn't create a project yourself, but another amasty.com account shared that project with you instead, you can also find it in License Registration tab, but in the Projects shared with me section:
In such shared projects, you have to manually generate your own pair of composer keys by clicking the Generate New Access Key button:
Project Owner account (the one that created the project) can generate as many composer key pairs as they need there, while other amasty.com accounts the project was shared with can generate only one pair of composer keys in the shared project, since they have limited permissions in it. Also, composer keys generated in one amasty.com account can't be viewed via another account.
It is possible to manually store the keys in the repository, eliminating the need for authorization every time. Find the Magento root directory and indicate:
Where $COMPOSER_AMASTY_USERNAMEis the Public Key and $COMPOSER_AMASTY_PASSWORD is the Private Key.
Alternatively, when prompted for access keys for the first time, you can authorize the system to save the credentials by typing yes.
The old functionality of storing composer keys on account level has been deprecated, those keys have been disabled, and they don't provide access to module download anymore. For this reason, it is necessary to switch to project-level composer keys according to our Composer guide. If you previously created composer keys on account level, the information below will help you locate them.
For viewing account-level composer keys generated in the past, navigate to the bottom of Products tab in your account:
Composer is the dependency manager that allows you easily download the required files on your server. The files are located on a remote server, or a repository, that you need to add to the list of “known” ones and authenticate to using the username ...
While updating Amasty extensions via composer, you may encounter a Nothing to install, update or remove message, as if there are no updates for the modules. There are several possible reasons why the composer is not fetching the latest version of the ...
Extension packages that introduce Hyva compatibility are available only by subscription model. Clients who purchased the module by product subscription or by one-time payment model before February 1, 2022, and subsequently activated the support ...
Follow these steps to install Amasty modules in your Magento environment: Step 1. To download and install Magento modules, the vendor repository is required. The Amasty repository can be added with the next command: composer config ...
Composer keys can’t be transferred or united once they're created. However, as an alternative option, you can create a License Registration project in one of your amasty.com accounts that will have its own composer keys, and share that project with ...
At Amasty, we understand that some of our clients require customized features to perfectly align the extension with their business needs. If you have developed new functionality within an Amasty module and would like to share it, please submit a ticket