How to use the new repo.magento.com
I've generated a new Magento Connect key per the developer documentation instructions. How am I supposed to use this key? i.e., if I try getting info, I see the following.
$ composer info magento/sample-data
Authentication required (repo.magento.com):
Username:
If I try following the new installation instructions, I get the same thing.
$ composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition magento2
Authentication required (repo.magento.com):
Username:
Is the key my password? If so, what's the username? If the key's a true key (i.e. no usename/password needed) where do I configure the key?
magento2 magento-connect
|
show 1 more comment
I've generated a new Magento Connect key per the developer documentation instructions. How am I supposed to use this key? i.e., if I try getting info, I see the following.
$ composer info magento/sample-data
Authentication required (repo.magento.com):
Username:
If I try following the new installation instructions, I get the same thing.
$ composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition magento2
Authentication required (repo.magento.com):
Username:
Is the key my password? If so, what's the username? If the key's a true key (i.e. no usename/password needed) where do I configure the key?
magento2 magento-connect
11
@Flyingmana The author did read through the documentation, and the documentation made no mention that a Magento key pair corresponds to composer username/password. Perhaps that's obvious to some, but it's not obvious to all.
– Alan Storm
Nov 20 '15 at 18:59
1
The documentation changed shortly after the GA. Out of the gate it required the account username/password (which I'm not sure work anymore), but then they updated it. Yeah…huge oversight, but at least it's using generated tokens now. :)
– davidalger
Nov 20 '15 at 22:54
I'll leave it to OP to close the question. Docs were updated after the fact.
– benmarks♦
Nov 21 '15 at 3:36
7
@Flyingmana seriously if we are going to close every question because somebody did not read the documentation.. then what is a purpose of stackexchange
– Pawel Dubiel
Nov 21 '15 at 21:17
1
What's the deal anyway with this login? Do they want to collect user accounts? I don't get it.
– tester
Dec 8 '15 at 7:02
|
show 1 more comment
I've generated a new Magento Connect key per the developer documentation instructions. How am I supposed to use this key? i.e., if I try getting info, I see the following.
$ composer info magento/sample-data
Authentication required (repo.magento.com):
Username:
If I try following the new installation instructions, I get the same thing.
$ composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition magento2
Authentication required (repo.magento.com):
Username:
Is the key my password? If so, what's the username? If the key's a true key (i.e. no usename/password needed) where do I configure the key?
magento2 magento-connect
I've generated a new Magento Connect key per the developer documentation instructions. How am I supposed to use this key? i.e., if I try getting info, I see the following.
$ composer info magento/sample-data
Authentication required (repo.magento.com):
Username:
If I try following the new installation instructions, I get the same thing.
$ composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition magento2
Authentication required (repo.magento.com):
Username:
Is the key my password? If so, what's the username? If the key's a true key (i.e. no usename/password needed) where do I configure the key?
magento2 magento-connect
magento2 magento-connect
edited Dec 16 '15 at 15:11
Anna Völkl
15.5k345132
15.5k345132
asked Nov 20 '15 at 18:29
Alan StormAlan Storm
28.7k18115303
28.7k18115303
11
@Flyingmana The author did read through the documentation, and the documentation made no mention that a Magento key pair corresponds to composer username/password. Perhaps that's obvious to some, but it's not obvious to all.
– Alan Storm
Nov 20 '15 at 18:59
1
The documentation changed shortly after the GA. Out of the gate it required the account username/password (which I'm not sure work anymore), but then they updated it. Yeah…huge oversight, but at least it's using generated tokens now. :)
– davidalger
Nov 20 '15 at 22:54
I'll leave it to OP to close the question. Docs were updated after the fact.
– benmarks♦
Nov 21 '15 at 3:36
7
@Flyingmana seriously if we are going to close every question because somebody did not read the documentation.. then what is a purpose of stackexchange
– Pawel Dubiel
Nov 21 '15 at 21:17
1
What's the deal anyway with this login? Do they want to collect user accounts? I don't get it.
– tester
Dec 8 '15 at 7:02
|
show 1 more comment
11
@Flyingmana The author did read through the documentation, and the documentation made no mention that a Magento key pair corresponds to composer username/password. Perhaps that's obvious to some, but it's not obvious to all.
– Alan Storm
Nov 20 '15 at 18:59
1
The documentation changed shortly after the GA. Out of the gate it required the account username/password (which I'm not sure work anymore), but then they updated it. Yeah…huge oversight, but at least it's using generated tokens now. :)
– davidalger
Nov 20 '15 at 22:54
I'll leave it to OP to close the question. Docs were updated after the fact.
– benmarks♦
Nov 21 '15 at 3:36
7
@Flyingmana seriously if we are going to close every question because somebody did not read the documentation.. then what is a purpose of stackexchange
– Pawel Dubiel
Nov 21 '15 at 21:17
1
What's the deal anyway with this login? Do they want to collect user accounts? I don't get it.
– tester
Dec 8 '15 at 7:02
11
11
@Flyingmana The author did read through the documentation, and the documentation made no mention that a Magento key pair corresponds to composer username/password. Perhaps that's obvious to some, but it's not obvious to all.
– Alan Storm
Nov 20 '15 at 18:59
@Flyingmana The author did read through the documentation, and the documentation made no mention that a Magento key pair corresponds to composer username/password. Perhaps that's obvious to some, but it's not obvious to all.
– Alan Storm
Nov 20 '15 at 18:59
1
1
The documentation changed shortly after the GA. Out of the gate it required the account username/password (which I'm not sure work anymore), but then they updated it. Yeah…huge oversight, but at least it's using generated tokens now. :)
– davidalger
Nov 20 '15 at 22:54
The documentation changed shortly after the GA. Out of the gate it required the account username/password (which I'm not sure work anymore), but then they updated it. Yeah…huge oversight, but at least it's using generated tokens now. :)
– davidalger
Nov 20 '15 at 22:54
I'll leave it to OP to close the question. Docs were updated after the fact.
– benmarks♦
Nov 21 '15 at 3:36
I'll leave it to OP to close the question. Docs were updated after the fact.
– benmarks♦
Nov 21 '15 at 3:36
7
7
@Flyingmana seriously if we are going to close every question because somebody did not read the documentation.. then what is a purpose of stackexchange
– Pawel Dubiel
Nov 21 '15 at 21:17
@Flyingmana seriously if we are going to close every question because somebody did not read the documentation.. then what is a purpose of stackexchange
– Pawel Dubiel
Nov 21 '15 at 21:17
1
1
What's the deal anyway with this login? Do they want to collect user accounts? I don't get it.
– tester
Dec 8 '15 at 7:02
What's the deal anyway with this login? Do they want to collect user accounts? I don't get it.
– tester
Dec 8 '15 at 7:02
|
show 1 more comment
8 Answers
8
active
oldest
votes
add the following to your auth.json
file
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
14
Or enter your public key as the username and private key as the password at the prompts.
– Alan Storm
Nov 20 '15 at 18:38
1
@AlanStorm Thanks it's work.
– Nikunj Vadariya
Dec 7 '15 at 6:05
2
the file is in ~/.composer/auth.json and in magento root
– Claudiu Creanga
Jan 29 '16 at 16:02
You must generate keys from Magento Marketplace see devdocs.magento.com/guides/v2.0/install-gde/prereq/…
– himansu
Dec 8 '16 at 17:40
why is username called public key or vice versa? The prompt should ask for public key etc! Why create the confusion with different labels?
– Jon
Dec 19 '16 at 12:26
|
show 2 more comments
Previous example is correct. In addition... it's also possible by composer's config command.
composer.phar global config http-basic.repo.magento.com <public_key> <private_key>
Thanks! I'll probably add that to the documentation, which is recently updated: bit.ly/1SMMh9p
– Steve Johnson
Nov 20 '15 at 19:27
add a comment |
Previous examples are correct. In addition it is also possible by composer's config command.
Inside the Magento project directory execute the following Composer command:
$ composer config http-basic.repo.magento.com <public_key> <private_key>
Just replace the placeholders with the actual values (public_key will become the username and private_key the password in HTTP authentication with repo.magento.com).
The auth settings can be tested by using fetching latest version with a faked update:
$ composer update --dry-run
This will give an error message like:
Invalid credentials for 'https://repo.magento.com/packages.json', aborting.
if something is wrong with the credentials.
I can strongly suggest to manage credentials inside the project folder as my answer suggests. I also would not edit the auth.json
by hand but just with the composer command as it is less error-prone.
Where i can i add this : composer.phar config http-basic.repo.magento.com <public_key> <private_key>
– Gem
May 2 '18 at 9:30
@Rathinam You don't add it, you execute it. the command is "composer", see composer documentation on how to use that utility for all the details: getcomposer.org
– hakre
May 2 '18 at 14:14
add a comment |
Login in magento using your credentials.
Then follow the navigation
1.My Account
2.Marketplace
3.My Access Key
4.Magento2
Public Key: xxxxx
Private Key:xxxxx
Public Key used as user name and Private Key used as password.
add a comment |
All answers are good just to compile possible scenarios on a single place.
Magento announced a new way to communicate to marketplace via compsoer, when you run composer install
in the root directory of Magento it will prompt for username and password, remember this is not the Magento username and password it is Public and Private key of Magento Marketplace.
Login to Magento Marketplace.
Go to My Account.
Under My Products click Access Keys.
Select ver of Magento (1 or 2).
Click Create A New Access Key, in popup box name your key.
Clicking on Ok will generate pair of keys, Public and Private.
Now in Magento root or open ~/.composer/auth.json
and put following lines
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
You are good to go. Remember auth.json
file contains standard json if you see any error just make sure that your auth file contains valid json, you can validate your json on JsonLint
If you don't want to add this information in above mentioned file (although it is handy, you don't need to open Marketplace dashboard repeatedly), then on run time just enter your Public key as username and Private key as your password, if you didn't add pair of keys in auth.json
in previous step, don't worry Magento will ask you here whether to store this information or not, the choice is yours! :)
add a comment |
If this code will give error like auth.json does not contain valid JSON Parse error on line 1:
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
Than it will be like below:
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
Here You should Wrap your auth.json
File with extra {}
add a comment |
To Find Authentication username & password . Just follow below step
Authentication required (repo.magento.com):
Username:
Step 1. open https://marketplace.magento.com/customer/account/ & Login
Step 2. Click on 'My Profile'
Step 3. click 'Marketplace' Then Click 'My Access' link
Step 4. On My Access Keys page, click on 'Magento 2' tab
Step 5. click on 'Create A New Access Key' button
Then, you will get two keys Public and Private
Public Key is your username
Private Key is your password
Copy key
yes, its clear instruction
– matinict
Sep 17 '18 at 4:15
add a comment |
If you are trying from the command line interface :
Authentication required (repo.magento.com):
Username: "Your public key"
Password: "Your private key"
Remember here Username means "public key" and password means "private key"
Keep developing...
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f90983%2fhow-to-use-the-new-repo-magento-com%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
8 Answers
8
active
oldest
votes
8 Answers
8
active
oldest
votes
active
oldest
votes
active
oldest
votes
add the following to your auth.json
file
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
14
Or enter your public key as the username and private key as the password at the prompts.
– Alan Storm
Nov 20 '15 at 18:38
1
@AlanStorm Thanks it's work.
– Nikunj Vadariya
Dec 7 '15 at 6:05
2
the file is in ~/.composer/auth.json and in magento root
– Claudiu Creanga
Jan 29 '16 at 16:02
You must generate keys from Magento Marketplace see devdocs.magento.com/guides/v2.0/install-gde/prereq/…
– himansu
Dec 8 '16 at 17:40
why is username called public key or vice versa? The prompt should ask for public key etc! Why create the confusion with different labels?
– Jon
Dec 19 '16 at 12:26
|
show 2 more comments
add the following to your auth.json
file
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
14
Or enter your public key as the username and private key as the password at the prompts.
– Alan Storm
Nov 20 '15 at 18:38
1
@AlanStorm Thanks it's work.
– Nikunj Vadariya
Dec 7 '15 at 6:05
2
the file is in ~/.composer/auth.json and in magento root
– Claudiu Creanga
Jan 29 '16 at 16:02
You must generate keys from Magento Marketplace see devdocs.magento.com/guides/v2.0/install-gde/prereq/…
– himansu
Dec 8 '16 at 17:40
why is username called public key or vice versa? The prompt should ask for public key etc! Why create the confusion with different labels?
– Jon
Dec 19 '16 at 12:26
|
show 2 more comments
add the following to your auth.json
file
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
add the following to your auth.json
file
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
edited Feb 13 '18 at 15:38
Cedric
13411
13411
answered Nov 20 '15 at 18:34
MaddyMaddy
1,122613
1,122613
14
Or enter your public key as the username and private key as the password at the prompts.
– Alan Storm
Nov 20 '15 at 18:38
1
@AlanStorm Thanks it's work.
– Nikunj Vadariya
Dec 7 '15 at 6:05
2
the file is in ~/.composer/auth.json and in magento root
– Claudiu Creanga
Jan 29 '16 at 16:02
You must generate keys from Magento Marketplace see devdocs.magento.com/guides/v2.0/install-gde/prereq/…
– himansu
Dec 8 '16 at 17:40
why is username called public key or vice versa? The prompt should ask for public key etc! Why create the confusion with different labels?
– Jon
Dec 19 '16 at 12:26
|
show 2 more comments
14
Or enter your public key as the username and private key as the password at the prompts.
– Alan Storm
Nov 20 '15 at 18:38
1
@AlanStorm Thanks it's work.
– Nikunj Vadariya
Dec 7 '15 at 6:05
2
the file is in ~/.composer/auth.json and in magento root
– Claudiu Creanga
Jan 29 '16 at 16:02
You must generate keys from Magento Marketplace see devdocs.magento.com/guides/v2.0/install-gde/prereq/…
– himansu
Dec 8 '16 at 17:40
why is username called public key or vice versa? The prompt should ask for public key etc! Why create the confusion with different labels?
– Jon
Dec 19 '16 at 12:26
14
14
Or enter your public key as the username and private key as the password at the prompts.
– Alan Storm
Nov 20 '15 at 18:38
Or enter your public key as the username and private key as the password at the prompts.
– Alan Storm
Nov 20 '15 at 18:38
1
1
@AlanStorm Thanks it's work.
– Nikunj Vadariya
Dec 7 '15 at 6:05
@AlanStorm Thanks it's work.
– Nikunj Vadariya
Dec 7 '15 at 6:05
2
2
the file is in ~/.composer/auth.json and in magento root
– Claudiu Creanga
Jan 29 '16 at 16:02
the file is in ~/.composer/auth.json and in magento root
– Claudiu Creanga
Jan 29 '16 at 16:02
You must generate keys from Magento Marketplace see devdocs.magento.com/guides/v2.0/install-gde/prereq/…
– himansu
Dec 8 '16 at 17:40
You must generate keys from Magento Marketplace see devdocs.magento.com/guides/v2.0/install-gde/prereq/…
– himansu
Dec 8 '16 at 17:40
why is username called public key or vice versa? The prompt should ask for public key etc! Why create the confusion with different labels?
– Jon
Dec 19 '16 at 12:26
why is username called public key or vice versa? The prompt should ask for public key etc! Why create the confusion with different labels?
– Jon
Dec 19 '16 at 12:26
|
show 2 more comments
Previous example is correct. In addition... it's also possible by composer's config command.
composer.phar global config http-basic.repo.magento.com <public_key> <private_key>
Thanks! I'll probably add that to the documentation, which is recently updated: bit.ly/1SMMh9p
– Steve Johnson
Nov 20 '15 at 19:27
add a comment |
Previous example is correct. In addition... it's also possible by composer's config command.
composer.phar global config http-basic.repo.magento.com <public_key> <private_key>
Thanks! I'll probably add that to the documentation, which is recently updated: bit.ly/1SMMh9p
– Steve Johnson
Nov 20 '15 at 19:27
add a comment |
Previous example is correct. In addition... it's also possible by composer's config command.
composer.phar global config http-basic.repo.magento.com <public_key> <private_key>
Previous example is correct. In addition... it's also possible by composer's config command.
composer.phar global config http-basic.repo.magento.com <public_key> <private_key>
answered Nov 20 '15 at 18:39
cmuenchcmuench
68458
68458
Thanks! I'll probably add that to the documentation, which is recently updated: bit.ly/1SMMh9p
– Steve Johnson
Nov 20 '15 at 19:27
add a comment |
Thanks! I'll probably add that to the documentation, which is recently updated: bit.ly/1SMMh9p
– Steve Johnson
Nov 20 '15 at 19:27
Thanks! I'll probably add that to the documentation, which is recently updated: bit.ly/1SMMh9p
– Steve Johnson
Nov 20 '15 at 19:27
Thanks! I'll probably add that to the documentation, which is recently updated: bit.ly/1SMMh9p
– Steve Johnson
Nov 20 '15 at 19:27
add a comment |
Previous examples are correct. In addition it is also possible by composer's config command.
Inside the Magento project directory execute the following Composer command:
$ composer config http-basic.repo.magento.com <public_key> <private_key>
Just replace the placeholders with the actual values (public_key will become the username and private_key the password in HTTP authentication with repo.magento.com).
The auth settings can be tested by using fetching latest version with a faked update:
$ composer update --dry-run
This will give an error message like:
Invalid credentials for 'https://repo.magento.com/packages.json', aborting.
if something is wrong with the credentials.
I can strongly suggest to manage credentials inside the project folder as my answer suggests. I also would not edit the auth.json
by hand but just with the composer command as it is less error-prone.
Where i can i add this : composer.phar config http-basic.repo.magento.com <public_key> <private_key>
– Gem
May 2 '18 at 9:30
@Rathinam You don't add it, you execute it. the command is "composer", see composer documentation on how to use that utility for all the details: getcomposer.org
– hakre
May 2 '18 at 14:14
add a comment |
Previous examples are correct. In addition it is also possible by composer's config command.
Inside the Magento project directory execute the following Composer command:
$ composer config http-basic.repo.magento.com <public_key> <private_key>
Just replace the placeholders with the actual values (public_key will become the username and private_key the password in HTTP authentication with repo.magento.com).
The auth settings can be tested by using fetching latest version with a faked update:
$ composer update --dry-run
This will give an error message like:
Invalid credentials for 'https://repo.magento.com/packages.json', aborting.
if something is wrong with the credentials.
I can strongly suggest to manage credentials inside the project folder as my answer suggests. I also would not edit the auth.json
by hand but just with the composer command as it is less error-prone.
Where i can i add this : composer.phar config http-basic.repo.magento.com <public_key> <private_key>
– Gem
May 2 '18 at 9:30
@Rathinam You don't add it, you execute it. the command is "composer", see composer documentation on how to use that utility for all the details: getcomposer.org
– hakre
May 2 '18 at 14:14
add a comment |
Previous examples are correct. In addition it is also possible by composer's config command.
Inside the Magento project directory execute the following Composer command:
$ composer config http-basic.repo.magento.com <public_key> <private_key>
Just replace the placeholders with the actual values (public_key will become the username and private_key the password in HTTP authentication with repo.magento.com).
The auth settings can be tested by using fetching latest version with a faked update:
$ composer update --dry-run
This will give an error message like:
Invalid credentials for 'https://repo.magento.com/packages.json', aborting.
if something is wrong with the credentials.
I can strongly suggest to manage credentials inside the project folder as my answer suggests. I also would not edit the auth.json
by hand but just with the composer command as it is less error-prone.
Previous examples are correct. In addition it is also possible by composer's config command.
Inside the Magento project directory execute the following Composer command:
$ composer config http-basic.repo.magento.com <public_key> <private_key>
Just replace the placeholders with the actual values (public_key will become the username and private_key the password in HTTP authentication with repo.magento.com).
The auth settings can be tested by using fetching latest version with a faked update:
$ composer update --dry-run
This will give an error message like:
Invalid credentials for 'https://repo.magento.com/packages.json', aborting.
if something is wrong with the credentials.
I can strongly suggest to manage credentials inside the project folder as my answer suggests. I also would not edit the auth.json
by hand but just with the composer command as it is less error-prone.
edited May 2 '18 at 14:15
answered Apr 3 '16 at 14:37
hakrehakre
1,39721435
1,39721435
Where i can i add this : composer.phar config http-basic.repo.magento.com <public_key> <private_key>
– Gem
May 2 '18 at 9:30
@Rathinam You don't add it, you execute it. the command is "composer", see composer documentation on how to use that utility for all the details: getcomposer.org
– hakre
May 2 '18 at 14:14
add a comment |
Where i can i add this : composer.phar config http-basic.repo.magento.com <public_key> <private_key>
– Gem
May 2 '18 at 9:30
@Rathinam You don't add it, you execute it. the command is "composer", see composer documentation on how to use that utility for all the details: getcomposer.org
– hakre
May 2 '18 at 14:14
Where i can i add this : composer.phar config http-basic.repo.magento.com <public_key> <private_key>
– Gem
May 2 '18 at 9:30
Where i can i add this : composer.phar config http-basic.repo.magento.com <public_key> <private_key>
– Gem
May 2 '18 at 9:30
@Rathinam You don't add it, you execute it. the command is "composer", see composer documentation on how to use that utility for all the details: getcomposer.org
– hakre
May 2 '18 at 14:14
@Rathinam You don't add it, you execute it. the command is "composer", see composer documentation on how to use that utility for all the details: getcomposer.org
– hakre
May 2 '18 at 14:14
add a comment |
Login in magento using your credentials.
Then follow the navigation
1.My Account
2.Marketplace
3.My Access Key
4.Magento2
Public Key: xxxxx
Private Key:xxxxx
Public Key used as user name and Private Key used as password.
add a comment |
Login in magento using your credentials.
Then follow the navigation
1.My Account
2.Marketplace
3.My Access Key
4.Magento2
Public Key: xxxxx
Private Key:xxxxx
Public Key used as user name and Private Key used as password.
add a comment |
Login in magento using your credentials.
Then follow the navigation
1.My Account
2.Marketplace
3.My Access Key
4.Magento2
Public Key: xxxxx
Private Key:xxxxx
Public Key used as user name and Private Key used as password.
Login in magento using your credentials.
Then follow the navigation
1.My Account
2.Marketplace
3.My Access Key
4.Magento2
Public Key: xxxxx
Private Key:xxxxx
Public Key used as user name and Private Key used as password.
answered Apr 29 '17 at 1:42
Kishor HaseKishor Hase
518418
518418
add a comment |
add a comment |
All answers are good just to compile possible scenarios on a single place.
Magento announced a new way to communicate to marketplace via compsoer, when you run composer install
in the root directory of Magento it will prompt for username and password, remember this is not the Magento username and password it is Public and Private key of Magento Marketplace.
Login to Magento Marketplace.
Go to My Account.
Under My Products click Access Keys.
Select ver of Magento (1 or 2).
Click Create A New Access Key, in popup box name your key.
Clicking on Ok will generate pair of keys, Public and Private.
Now in Magento root or open ~/.composer/auth.json
and put following lines
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
You are good to go. Remember auth.json
file contains standard json if you see any error just make sure that your auth file contains valid json, you can validate your json on JsonLint
If you don't want to add this information in above mentioned file (although it is handy, you don't need to open Marketplace dashboard repeatedly), then on run time just enter your Public key as username and Private key as your password, if you didn't add pair of keys in auth.json
in previous step, don't worry Magento will ask you here whether to store this information or not, the choice is yours! :)
add a comment |
All answers are good just to compile possible scenarios on a single place.
Magento announced a new way to communicate to marketplace via compsoer, when you run composer install
in the root directory of Magento it will prompt for username and password, remember this is not the Magento username and password it is Public and Private key of Magento Marketplace.
Login to Magento Marketplace.
Go to My Account.
Under My Products click Access Keys.
Select ver of Magento (1 or 2).
Click Create A New Access Key, in popup box name your key.
Clicking on Ok will generate pair of keys, Public and Private.
Now in Magento root or open ~/.composer/auth.json
and put following lines
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
You are good to go. Remember auth.json
file contains standard json if you see any error just make sure that your auth file contains valid json, you can validate your json on JsonLint
If you don't want to add this information in above mentioned file (although it is handy, you don't need to open Marketplace dashboard repeatedly), then on run time just enter your Public key as username and Private key as your password, if you didn't add pair of keys in auth.json
in previous step, don't worry Magento will ask you here whether to store this information or not, the choice is yours! :)
add a comment |
All answers are good just to compile possible scenarios on a single place.
Magento announced a new way to communicate to marketplace via compsoer, when you run composer install
in the root directory of Magento it will prompt for username and password, remember this is not the Magento username and password it is Public and Private key of Magento Marketplace.
Login to Magento Marketplace.
Go to My Account.
Under My Products click Access Keys.
Select ver of Magento (1 or 2).
Click Create A New Access Key, in popup box name your key.
Clicking on Ok will generate pair of keys, Public and Private.
Now in Magento root or open ~/.composer/auth.json
and put following lines
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
You are good to go. Remember auth.json
file contains standard json if you see any error just make sure that your auth file contains valid json, you can validate your json on JsonLint
If you don't want to add this information in above mentioned file (although it is handy, you don't need to open Marketplace dashboard repeatedly), then on run time just enter your Public key as username and Private key as your password, if you didn't add pair of keys in auth.json
in previous step, don't worry Magento will ask you here whether to store this information or not, the choice is yours! :)
All answers are good just to compile possible scenarios on a single place.
Magento announced a new way to communicate to marketplace via compsoer, when you run composer install
in the root directory of Magento it will prompt for username and password, remember this is not the Magento username and password it is Public and Private key of Magento Marketplace.
Login to Magento Marketplace.
Go to My Account.
Under My Products click Access Keys.
Select ver of Magento (1 or 2).
Click Create A New Access Key, in popup box name your key.
Clicking on Ok will generate pair of keys, Public and Private.
Now in Magento root or open ~/.composer/auth.json
and put following lines
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
You are good to go. Remember auth.json
file contains standard json if you see any error just make sure that your auth file contains valid json, you can validate your json on JsonLint
If you don't want to add this information in above mentioned file (although it is handy, you don't need to open Marketplace dashboard repeatedly), then on run time just enter your Public key as username and Private key as your password, if you didn't add pair of keys in auth.json
in previous step, don't worry Magento will ask you here whether to store this information or not, the choice is yours! :)
edited Jan 19 '18 at 20:42
answered Nov 28 '17 at 17:18
AdnanAdnan
194110
194110
add a comment |
add a comment |
If this code will give error like auth.json does not contain valid JSON Parse error on line 1:
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
Than it will be like below:
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
Here You should Wrap your auth.json
File with extra {}
add a comment |
If this code will give error like auth.json does not contain valid JSON Parse error on line 1:
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
Than it will be like below:
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
Here You should Wrap your auth.json
File with extra {}
add a comment |
If this code will give error like auth.json does not contain valid JSON Parse error on line 1:
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
Than it will be like below:
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
Here You should Wrap your auth.json
File with extra {}
If this code will give error like auth.json does not contain valid JSON Parse error on line 1:
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
Than it will be like below:
{
"http-basic": {
"repo.magento.com": {
"username":"<your public key>",
"password":"<your private key>"
}
}
}
Here You should Wrap your auth.json
File with extra {}
answered Jul 6 '17 at 6:11
Nirav JoshiNirav Joshi
8213
8213
add a comment |
add a comment |
To Find Authentication username & password . Just follow below step
Authentication required (repo.magento.com):
Username:
Step 1. open https://marketplace.magento.com/customer/account/ & Login
Step 2. Click on 'My Profile'
Step 3. click 'Marketplace' Then Click 'My Access' link
Step 4. On My Access Keys page, click on 'Magento 2' tab
Step 5. click on 'Create A New Access Key' button
Then, you will get two keys Public and Private
Public Key is your username
Private Key is your password
Copy key
yes, its clear instruction
– matinict
Sep 17 '18 at 4:15
add a comment |
To Find Authentication username & password . Just follow below step
Authentication required (repo.magento.com):
Username:
Step 1. open https://marketplace.magento.com/customer/account/ & Login
Step 2. Click on 'My Profile'
Step 3. click 'Marketplace' Then Click 'My Access' link
Step 4. On My Access Keys page, click on 'Magento 2' tab
Step 5. click on 'Create A New Access Key' button
Then, you will get two keys Public and Private
Public Key is your username
Private Key is your password
Copy key
yes, its clear instruction
– matinict
Sep 17 '18 at 4:15
add a comment |
To Find Authentication username & password . Just follow below step
Authentication required (repo.magento.com):
Username:
Step 1. open https://marketplace.magento.com/customer/account/ & Login
Step 2. Click on 'My Profile'
Step 3. click 'Marketplace' Then Click 'My Access' link
Step 4. On My Access Keys page, click on 'Magento 2' tab
Step 5. click on 'Create A New Access Key' button
Then, you will get two keys Public and Private
Public Key is your username
Private Key is your password
Copy key
To Find Authentication username & password . Just follow below step
Authentication required (repo.magento.com):
Username:
Step 1. open https://marketplace.magento.com/customer/account/ & Login
Step 2. Click on 'My Profile'
Step 3. click 'Marketplace' Then Click 'My Access' link
Step 4. On My Access Keys page, click on 'Magento 2' tab
Step 5. click on 'Create A New Access Key' button
Then, you will get two keys Public and Private
Public Key is your username
Private Key is your password
Copy key
answered Jul 18 '18 at 11:58
ShorabhShorabh
500214
500214
yes, its clear instruction
– matinict
Sep 17 '18 at 4:15
add a comment |
yes, its clear instruction
– matinict
Sep 17 '18 at 4:15
yes, its clear instruction
– matinict
Sep 17 '18 at 4:15
yes, its clear instruction
– matinict
Sep 17 '18 at 4:15
add a comment |
If you are trying from the command line interface :
Authentication required (repo.magento.com):
Username: "Your public key"
Password: "Your private key"
Remember here Username means "public key" and password means "private key"
Keep developing...
New contributor
add a comment |
If you are trying from the command line interface :
Authentication required (repo.magento.com):
Username: "Your public key"
Password: "Your private key"
Remember here Username means "public key" and password means "private key"
Keep developing...
New contributor
add a comment |
If you are trying from the command line interface :
Authentication required (repo.magento.com):
Username: "Your public key"
Password: "Your private key"
Remember here Username means "public key" and password means "private key"
Keep developing...
New contributor
If you are trying from the command line interface :
Authentication required (repo.magento.com):
Username: "Your public key"
Password: "Your private key"
Remember here Username means "public key" and password means "private key"
Keep developing...
New contributor
New contributor
answered 5 mins ago
gurcharangurcharan
1
1
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f90983%2fhow-to-use-the-new-repo-magento-com%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
11
@Flyingmana The author did read through the documentation, and the documentation made no mention that a Magento key pair corresponds to composer username/password. Perhaps that's obvious to some, but it's not obvious to all.
– Alan Storm
Nov 20 '15 at 18:59
1
The documentation changed shortly after the GA. Out of the gate it required the account username/password (which I'm not sure work anymore), but then they updated it. Yeah…huge oversight, but at least it's using generated tokens now. :)
– davidalger
Nov 20 '15 at 22:54
I'll leave it to OP to close the question. Docs were updated after the fact.
– benmarks♦
Nov 21 '15 at 3:36
7
@Flyingmana seriously if we are going to close every question because somebody did not read the documentation.. then what is a purpose of stackexchange
– Pawel Dubiel
Nov 21 '15 at 21:17
1
What's the deal anyway with this login? Do they want to collect user accounts? I don't get it.
– tester
Dec 8 '15 at 7:02