How to switch to project-level composer keys from old account-level keys?

How to switch to project-level composer keys from old account-level keys?

The option of creating composer keys in Products tab of amasty.com accounts was deprecated, and such account-level keys have been deactivated. This means that Amasty extensions can't be downloaded using such keys anymore. To avoid any service interruptions, it is necessary to switch to project-level composer keys.

Step 1. Ensure that you created a project in License Registration tab and assigned the extensions you wish to download to it. The process is described in detail in the following guide;
Notes
Project-level composer keys grant access to downloading only those extensions that are assigned to the project the keys originate from. If an extension license isn't assigned to any project, it will be unavailable for download.

Step 2. Align the composer keys used in your Magento environment with the keys saved in your project. This can be carried out using either of the alternative options below:
  1. You can migrate your account-level keys to project level, this approach won't require changing anything in Magento. Proceed to Products tab of your amasty.com account, scroll down to the Access Keys section and click on Migrate link next to the key pair:

    A popup will appear where you'll need to select which project your keys will be moved to. Confirm your choice after selecting the necessary project from the dropdown:

    That's it! The keys that previously resided in Products tab will disappear from there:

    Instead, they'll be present in selected project, where they'll be added to already existing project-level keys, if you have any. To mark the migration process, old keys will have "migrated" added next to them:
Alert
If your account-level composer keys have been automatically disabled and after that you decide to migrate them to project level, please note that migrated keys will still have Disabled status when they appear in a project:











Thus, after you migrate account-level composer keys to project level, please enable them, if needed.

  1. Or, you can save the new composer keys generated from your project in your Magento environment. For this, open project details by clicking on View link next to it:

    The page will contain Composer Access Keys section with project-level keys. You will need to copy Public key and Private Key:

    Currently composer keys are generated automatically when a project is created, but earlier projects were created without them. If you don't have composer keys inside project details, they can be generated in the same Composer Access Keys section:

    In your root Magento directory, run the following command, replacing $COMPOSER_AMASTY_USERNAME with your Public Key and  $COMPOSER_AMASTY_PASSWORD with your Private Key:
    composer config --auth http-basic.composer.amasty.com $COMPOSER_AMASTY_USERNAME $COMPOSER_AMASTY_PASSWORD