transfer action requires authorization of collection author

[imb590]

I deployed the contract on a dev blockchain with the same code atomicassets account currently has on the WAX blockchain, set permissions for @eosio.code authorization and triggered the init action. After that most actions work as expected, but when I trigger transfer without the authorization from asset's collection's author, it fails with missing_auth_exception and demands that authorization.

What can cause such behavior?

[imb590]

After a bit of digging, it turned out that the authorization is demanded on this step:

        to_assets.emplace(asset_itr->ram_payer, [&](auto &_asset) {
            _asset.asset_id = asset_itr->asset_id;
            _asset.collection_name = asset_itr->collection_name;
            _asset.schema_name = asset_itr->schema_name;
            _asset.template_id = asset_itr->template_id;
            _asset.ram_payer = asset_itr->ram_payer;
            _asset.backed_tokens = asset_itr->backed_tokens;
            _asset.immutable_serialized_data = asset_itr->immutable_serialized_data;
            _asset.mutable_serialized_data = asset_itr->mutable_serialized_data;
        });

assetitr->ram_payer is the account that minted the asset, and its authorization is required for each transfer on my local blockchain. Obviously, this does not happen on the main chain. Why? What's the difference? How to set up a local blockchain so it behaves the same as the main one?