Password authentification and ssh

[hafid-hub]

Thank you for this project.
I have some troubles : when I want to push changes to GitHub, I get this message:

Password for 'https://[email protected]': 
remote: Support for password authentication was removed on August 13, 2021.

I use ssh and it stills ask me for my username and password.

🎯 Goal
Since password authentication has been removed, it is better, in my opinion, to take this into account in this admirable tutorial. I think that a user, like me who is just starting to learn to code, could quickly get discouraged, especially since he has almost reached his goal. And if he used, like me ssh, he will be asked again and again for the password.

💡 Possible solutions
I overcome this problem with this command:
git remote set-url origin [[email protected]](mailto:[email protected]):<Username>/<Project>.git

[JainitBITW]

you can try creating a personal token and use it as a password

[doczkal]

you can try creating a personal token and use it as a password

What is the reason the setup of Public+private key authentication is not mentioned?
It would certainly make the process of git-push much simpler.

[MD-ARBAB-SAHID]

💡 Possible solution
1 . Generate a personal token by navigating:
Settings > Developer settings > Personal access tokens
2. Then generate a new token by clicking on "Generate new token" and then fill the token configuration details like Note(acts like a label to remind you for what reason the token was created) , adding expiry of the token and the scopes(permissions).
3. Click on Generate token.
4. Copy the token generated as it will be available only for the first time.
5. Use that token instead of your password.

[abhint1]

can you assign me this issue

[yellowsamuray]

I had same problem. But then I tried again by making sure to clone with the SSH link, not the HTTPS link

[Esh07]

This is a beginner tutorial, I would advise against including SSH configuration.

Configuring SSH can be intimidating for new users, especially those who are not familiar with GitHub or terminal commands. Instead, I suggest sticking with HTTPS, as it is straightforward and only requires a Personal Access Token (PAT) for authentication.

This approach would be more user-friendly for beginners. If want, we can provide an additional tutorial specifically focused on SSH configuration and add a link to it. That's my thought on it.

[JainitBITW]

A tutorial might help Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Esh ***@***.***> Sent: Tuesday, June 27, 2023 9:31:10 PM To: firstcontributions/first-contributions ***@***.***> Cc: Bafna Jainit Sushil ***@***.***>; Comment ***@***.***> Subject: Re: [firstcontributions/first-contributions] Password authentification and ssh (Issue #54360) This is a beginner tutorial, I would advise against including SSH configuration. Configuring SSH can be intimidating for new users, especially those who are not familiar with GitHub or terminal commands. Instead, I suggest sticking with HTTPS, as it is straightforward and only requires a Personal Access Token (PAT) for authentication. This approach would be more user-friendly for beginners. If want, we can provide an additional tutorial specifically focused on SSH configuration and add a link to it. That's my thought on it. — Reply to this email directly, view it on GitHub<#54360 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWXKKITGRZBBS5ODYVJ3WFLXNL7UNANCNFSM6AAAAAAQUMJZYM>. You are receiving this because you commented.Message ID: ***@***.***>

[JainitBITW]

For ssh Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Bafna Jainit Sushil ***@***.***> Sent: Tuesday, June 27, 2023 9:32:53 PM To: firstcontributions/first-contributions ***@***.***>; firstcontributions/first-contributions ***@***.***> Cc: Comment ***@***.***> Subject: Re: [firstcontributions/first-contributions] Password authentification and ssh (Issue #54360) A tutorial might help Get Outlook for Android<https://aka.ms/AAb9ysg>

________________________________ From: Esh ***@***.***> Sent: Tuesday, June 27, 2023 9:31:10 PM To: firstcontributions/first-contributions ***@***.***> Cc: Bafna Jainit Sushil ***@***.***>; Comment ***@***.***> Subject: Re: [firstcontributions/first-contributions] Password authentification and ssh (Issue #54360) This is a beginner tutorial, I would advise against including SSH configuration. Configuring SSH can be intimidating for new users, especially those who are not familiar with GitHub or terminal commands. Instead, I suggest sticking with HTTPS, as it is straightforward and only requires a Personal Access Token (PAT) for authentication. This approach would be more user-friendly for beginners. If want, we can provide an additional tutorial specifically focused on SSH configuration and add a link to it. That's my thought on it. — Reply to this email directly, view it on GitHub<#54360 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AWXKKITGRZBBS5ODYVJ3WFLXNL7UNANCNFSM6AAAAAAQUMJZYM>. You are receiving this because you commented.Message ID: ***@***.***>

[Esh07]

You're right, and I completely agree. I commented on this in the context of the README.md file; it only mentions and provides a link for SSH configuration. We can improve the README.md file by including an optional link for configuring SSH and recommending them Personal Access Token (PAT) with a link to the official doc.