I keep my extensions under different amasty.com accounts. How do I manage the Composer keys?
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 the rest of amasty.com accounts your extensions are located under. Then you can assign the rest of these extensions to the shared project, and all packages will be downloaded using a single pair of composer keys from your project. Please refer to the corresponding FAQ post for more details about this option.
As the next step of sharing, if you want all extensions to be situated under the same amasty.com account, you can perform full module transfer from one amasty.com account to another. Our guide on transfer process is available in this post.
Related Articles
How to merge our amasty.com accounts?
We don't have a technical option to merge accounts, however, access to the extension listed in one account can be granted for another account via project sharing. The account that wants to use the modules can share their project with the account that ...
Where can I find Composer access keys?
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 tab inside ...
How do I share my modules with another amasty.com account for download and registration?
We've introduced a feature that allows all users to share license registration projects listed in one customer account to another. As a result, both accounts will be able to assign modules to it, copy the project's Instance Registration Key and ...
I've got shared orders in my amasty.com account, how do I move them to projects?
Due to optimizing module download and registration processes, we have deprecated the old order sharing feature. If alternative configuration via project level isn't arranged, access to downloading shared extensions won't be possible via old ...
I’ve updated the modules via composer and I got the Autoload error: Module 'Amasty_Base' has been already defined.
Such errors can appear if the module you're trying to install or update is already present in Magento installation under some other path. In other words, there's a duplicate with the exact same files, but it is located in another directory. ...