Why do I keep getting a "Repository authentication failed, check credentials. Make sure the user has both read and write access" error message when I create a branch in studio signed in as system admin?

[5vetlana]

I am working on the NeedIt tutorial in the New to Service Now trainings.   Although I was able to do the previous steps I am unable to create a branch in the studio.   The instructions say:

Create a Branch from a Tag

1. In Studio, open the Source Control menu and select the Create Branch menu item.
2. Configure the Branch.               Branch Name CreateNeedItApp               Create from Tag: LoadForCreateNIAppModule
3. Click the Create Branch button.
4. Click the Close Dialog button.
5. After the branch is created, the branch name appears in the Studio status bar (bottom right corner).

When I try to run this in studio it fails with the error message "Repository authentication failed, check credentials. Make sure the user has both read and write access'   I have tried to sign in as various users that have read and write access but can't get it to work.   Can anyone tell me what I'm doing wrong?

[GhatakNow]

Alright, if you are facing this challenge, then please check the following.
1. Branch name : Your branch name may be Master not main . In the documentation it talks about main.

Best thing remove credentials and restart from scratch and it generally works.

[vikramhande]

https://docs.catalyst.zoho.com/en/tutorials/githubbot/java/generate-personal-access-token/#:~:text=Y....

copy this generated token and paste it in password while adding in repository

[Joe D_Souza]

I am getting this exact same error.. Just to eliminate the usual suspects:-

1) I am using the username and password used to create my GitHub account.

2) I do not have 2 factor authentication enabled.

3) To eliminate the possibility of mistyped username or password, I literally copied and pasted it from my browsers password manager record which is used successfully to login into GitHub directly from my browser..

So it cannot be that I am mistakenly using a ServiceNOW user admin username or password accidentally or that I am mistyping the username or password or that the username or password in the browsers password manager is an older record..

I am going through the instructions given in the "Exercise: Create and Link a Repository" exercise literally crossing the T's and dotting the I's. To the point that I replace the default branch that is suggested when creating the record with "master" that is suggested in the exercise...

Is it that this branch needs to first be created in GitHub? Because if so, that has not been done as there was no previous exercise to create one.. That is the only one thing I can think of.. and if that is what it is, I do not know how to create one in Git as I am fairly new to using Git..

Yet I get that error..

[Joe D_Souza]

With a suggestion of one of my friend who is a developer, he suggested not to use the GitHub password but create a token instead and use a token...

I had not tried this because the documentation on the website tutorials for the source code control section said either password or token and having not yet created a token for anything, was using the password.. This friend of mine suggested I create a token and use the token instead of the password.. So while creating the token I saw options for controlling read and write to a GitHub repository. I selected those options and created a token, and used that.. this worked so now I see the record that was needed to be created..

Thanks for anyone who may have put in some time to read about my problem,,

So maybe someone needs to correct that documentation on the tutorial and remove reference to using the GitHub username and password or token and have only GitHub username and token instead..

[sanketkambl]

Hi, in addition to the methods mentioned above, you can also check if you're using a Personal Access Token (PAT). You can create one by going to GitHub > Settings > Developer settings > Personal Access Token.

When entering credentials, use your GitHub username as the login and the Personal Access Token in the password field. Then, click Submit and try importing again.

Hope this helps! If you found this useful, please consider giving a thumbs up.