Composer Access Keys deprecation and switch to In-Project Composer Keys

As of January 1, 2026, Amasty will permanently disable all Composer access keys generated in the "Products" tab. These global keys will no longer grant access to Amasty packages via Composer.

Going forward, Composer access will be managed exclusively through project-based (in-project) keys.

We recommend making the switch to in-project Composer access keys before January 1, 2026, to avoid service disruptions.

Why is this change being made?

Composer keys generated in the “Products” tab apply globally to your entire account. This created several limitations and risks, especially for large teams, agencies, and clients with long-term project maintenance needs. 

Here are the common downsides of global keys we’ve become aware of:

• Version conflicts across different projects

• Security risks due to wide access

• Team collaboration issues, especially for agencies and larger teams

• No separation by project, making license management harder

• Unclear billing and access rights when using shared orders or multiple clients

What are in-project Composer keys?

In-project Composer keys are access credentials tied to individual projects in your Amasty account.
Each project has its own set of keys, bringing such benefits as:

• Clean version separation between projects

• More secure and scoped access

• Easier license and user management

• Better organization by client or use case

How to Switch to In-Project Composer Keys

Step 1. Assign your products to their respective projects
Ensure all your products are correctly assigned to projects within the "License Registration" tab.

Step 2. Switch to in-project Composer keys
After assigning your products, start using in-project Composer keys to manage your licenses. You can save these keys manually in your repository, eliminating the need for repeated authorization.

Find the Magento root directory and indicate:

composer config --auth http-basic.composer.amasty.com $COMPOSER_AMASTY_USERNAME $COMPOSER_AMASTY_PASSWORD

Where $COMPOSER_AMASTY_USERNAME is the Public Key and $COMPOSER_AMASTY_PASSWORD is the Private Key.

Read More: How to Generate Composer Access Keys for Amasty Extensions