Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authentication failed #220

Closed
phifuh opened this issue Jul 27, 2024 · 7 comments
Closed

Authentication failed #220

phifuh opened this issue Jul 27, 2024 · 7 comments
Labels
bug Something isn't working wait for reply

Comments

@phifuh
Copy link

phifuh commented Jul 27, 2024

I tried pushing a commit to my github repo, but I only get the error "authentication not supported"

I am currently using github desktop where I can push it to the repo.
I read in the issue #204 #205 that you have to install the gcm but even after installing i am not getting a "pop window" to login/create the acces token. I might need to config it by the CLI?

Anyway, even tho this might not be a "bug" - "bug", I still think gitnuro should make the process of authentication easier and guide the user. Not everyone will use CLI or read in past issues on github

@phifuh phifuh added the bug Something isn't working label Jul 27, 2024
@phifuh
Copy link
Author

phifuh commented Jul 28, 2024

I cant get the auth to work. I edited the "/etc/gitconfig" file & my normal git is working both in terminal & github desktop. Like I said earlier, it would be awesome if Gitnuro would have a better authentication service build into the app

@JetpackDuba
Copy link
Owner

Hey!

Can you post your gitconfig?

It's in the roadmap to add support for third party services at some point (as seen in #205) but not in the near future. However, improving the error could be something interesting and it was added to #30 .

It wasn't working out of the box because it probably used some kind of GitHub-specific auth such as GH CLI. Gitnuro 1.4 fixes some issues with GH CLI auth but it's not out yet (planned this week tho, release notes are ready).

@phifuh
Copy link
Author

phifuh commented Aug 9, 2024

[core]
	autocrlf = true
	excludesfile = C:\\Users\\___\\Documents\\gitignore_global.txt
	longpaths = true
[user]
	name = ___
	email = ___
[difftool "sourcetree"]
	cmd = '' \"$LOCAL\" \"$REMOTE\"
[mergetool "sourcetree"]
	cmd = "'' "
	trustExitCode = true
[filter "lfs"]
	process = git-lfs filter-process
	required = true
	clean = git-lfs clean -- %f
	smudge = git-lfs smudge -- %f
[safe]
	directory = C:/Users/___/AppData/Roaming/......
[credential]
	helper = wincred
[global]

@JetpackDuba
Copy link
Owner

Sorry for the late response.

The helper has to point to the Git Credentials Manager full path as shown in the readme FAQ.

I know it's not the best way tho. I've been experimenting a bit to avoid all this extra config/overhead but it needs more testing.

Given that I'm waiting for the release of a dependency, I'll try to test it further to avoid all these issues with users migrating from github cli or other credentials helpers.

@Ashutosh-pixel
Copy link

Ashutosh-pixel commented Sep 4, 2024

@JetpackDuba

#204 #205
Hey!,
I have attached 2 short videos. I m getting Authentication failed error whenever i trying to clone or push the repo online(GitHub).

link1 : clone auth problem
link2 : push repo auth problem

@JetpackDuba
Copy link
Owner

Don't use your password, you have to generate a token in GitHub that will be used for auth. I will have to add a warning as this issue arises often...

https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens

@Ashutosh-pixel
Copy link

@JetpackDuba

yes please add warning or something because every new user facing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working wait for reply
Projects
None yet
Development

No branches or pull requests

3 participants