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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2017 06:21 AM
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
- In Studio, open the Source Control menu and select the Create Branch menu item.
- Configure the Branch. Branch Name CreateNeedItApp Create from Tag: LoadForCreateNIAppModule
- Click the Create Branch button.
- Click the Close Dialog button.
- 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?
- Labels:
-
Studio
- 26,865 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2018 09:38 AM
My org requires 2FA (we have 1000's of non SN apps out there and we would be stupid not to). Has anyone been able to get it to work with 2FA enabled, or does it only work when 2FA is disabled?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2018 10:30 AM
If anyone is having the 2FA issue, you will need to use a "personal token" instead of your actual password. It's under settings -> developer settings -> personal access tokens on the Git side. Generate and use that as your password when trying to connect and you should be good to go.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2018 04:40 PM
This actually was the fix. Thx Jason.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2019 08:42 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-09-2021 07:38 AM
Fixed the issue for me alos... Thanks bunches!! Went round and round with this until I got here. I am NOT USING 2FA , but still was getting the auth failures. When I did this, it finally worked!!