Sample Data Installation issue

[pratikindia143]

I am trying to install sample data, but unable to install i tried following command
bin/magento sampledata:deploy
I am getting error as
[Composer\Downloader\TransportException] The 'https://repo.magento.com/packages.json' URL required authentication. You must be using the interactive console to authenticate

Even i am not getting prompt to enter username and password i.e public key and private key.
Is there any way i can include auth.json if yes please provide us sample auth and path. i have already added auth.json under /home/{user}/.composer/ folder or any other way to force the prompt for username and password.

I already tried composer update but no luck.

Please let me know is there anything else i have to do.

[nkarthickannan]

@pratikindia143

Please use the following commands:

1. bin/magento sampledata:deploy => throws error
2. composer update
3. bin/magento setup:upgrade
4. sudo chown -R :www-data .
5. sudo find . -type d -exec chmod 770 {} ; && sudo find . -type f -exec chmod 660 {} ; && sudo chmod u+x bin/magento

Thanks

[pratikindia143]

@karthickannan
Thanks, it worked, but still not clear even with the error bin/magento sampledata:deploy => throws error it worked fine?

[nkarthickannan]

@pratikindia143

I'm also not clear why that error is being thrown. If anybody knows the reason, please do let us know.

Thanks

The authentication error is caused by the fact that repo.magento.com requires authentication and the sample data modules (incorrectly) suppress the error from Composer. Your remediation steps are correct.

[nkarthickannan]

@xcomSteveJohnson

Thank you Steve. But I have the public and private keys added in my auth.json file. Then why the error is still popping up?

[dmitrii-fediuk]

Maybe your auth.json is wrong: maybe it contains a syntax error or maybe is placed in a wrong location.
See the documentation: http://devdocs.magento.com/guides/v2.0/install-gde/prereq/dev_install.html#create-authjson
Here is my working example for a custom private composer repository with the http-basic authentication: https://mage2.pro/t/256

[nkarthickannan]

@dfediuk

Here is my auth.json file content:

{
    "github-oauth": {
        "github.com": "<snip>"
    },
    "http-basic": {
        "repo.magento.com": {
            "username": "<snip>",
            "password": "<snip>"
        }
    }
}

I am able to get the Magento 2 code base using composer. So, we can conclude that both the username & password are valid and the auth.json is also valid.

Thanks

[dmitrii-fediuk]

Maybe the Composer does not see your auth.json file?

[nkarthickannan]

@dfediuk

As I told earlier, I'm able to get the Magento 2 project using this command composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition mage2

Also the auth.json file is in ~/.composer directory which is the composer home.

Thanks

[moleman]

I have the same problem and I have found the reason and a workaround.

The reason why sampledata:deploy will not read auth from your ~/.composer folder is because the COMPOSER_HOME environment variable is set by the MagentoComposerApplication class in the magento/composer package (source code / repo for this package doesn't seem to be publicly available?) and this class is constructed when running the sampledata:deploy command, even though it is not really used by the command from what I can see because the command itself will create a clean Composer\Console\Application object.

The class will set the COMPOSER_HOME environment variable to /var/composer_home so when sampledata:deploy is calling composer require, with the use of Composer\Console\Application, it will look for the auth.json in that folder.

A workaround for this is to copy your ~/.composer/auth.json (if it contains the correct authentication credentials) to var/composer_home before running sampledata:deploy but I would rather prefer sampledata:deploy to use the global Composer directory.

[Vinai]

Great debugging @moleman

[FossPrime]

I can Confirm @moleman 's solution works perfectly. Also, you don't need to copy it, a symbolic link will do the job just as well if not better.
ln -s ~/.composer/auth.json var/composer_home/

[nkarthickannan]

@moleman Great discovery!!

@Vinai As per @moleman comment, the un-used MagentoComposerApplication class is setting the COMPOSER_HOME variable. If the class is not at all useful then why should Magento use this class to create a new problem? If there is any reason for using this class please let us know. Otherwise usage of this class should be avoided to prevent this issue from popping-out.

Thanks

[TommyKolkman]

I applied @moleman's solution and ran magento sampledata:deploy. It now just silently fails.

~/Sites/magento-sandbox => magento sampledata:deploy
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
✘ => ~/Sites/magento-sandbox`

Anyone else with this problem?