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?

[Nick Fajardo]

https://github.blog/2020-12-15-token-authentication-requirements-for-git-operations/

You can't use a regular password for github anymore.  You need to setup ssh or a personal access token as mentioned by scott above

[tezpal]

Hi Ivonne,

Follow above Scott's screen shots (posted 2y ago), that worked for me.

We have to get the new token from GitHub and use it in our credentials instead of the regular GitHub password !

Thanks

Tez

[Ivonne Roque]

Thank you all!

[Doanna]

I had this issue, even when MFA was disabled. I used the GitHub Credentials on the Credential and Aliases Page, still was having the issue.

From Qubec Version onwards, you will have to activate personal access tokens.

From your GitHub home page , Navigate to Your profile on the Top Right corner >> Setting >> Developer Settings >>Personal access tokens >> activate your token and copy the token number.

Save it as your password under credentials in the ServiceNow instance

[nagydan2]

Thanks Doanna. This solved for me.