Authentication failed for Azure Git

Question

I'm trying to clone my webapp in Azure.

When I run git clone https://username@appname.scm.azurewebsites.net:443/appname.git the terminal asks me for my password.

But when I fill in my password, it keeps saying that the authentication has failed.

Even though I changed my password plenty of times in the Portal (Settings -> Set deployment credentials).

Any reason it keeps saying that my authentication has failed?

score 107 · Answer 1 · edited Aug 24 '22 at 17:37

Yes many of the answers here are pointing to the correct path, but my case:- I was given a url to access git repos on azure cloud for which I'm perfectly fine to access/browse the code on browser (Vs) when I'm trying to clone I've got the same issue.

So when you click on clone as shown in below image, you've got to Generate Git credentials; this is weird, not sure why, probably they've setup my account to access azure cloud, which can't be used to clone git repos(means can't be used as git credentials). This is something different from what I've seen with AWS/gitlab/bitbucket, maybe an issue with account setup, or if it's common thing for repos on Azure and if you're in same issue - give it a try.

Another one, as everyone has already mentioned, please don't try to connect to url which is produced over there (something looks like):

https://project-account@dev.azure.com/project-name/apps/_git/library/

Instead try to connect thru your GIT username and then use password:

https://username@dev.azure.com/project-name/apps/_git/library/

As a tip: if your username has special characters in it, Git cmd/bash will throw errors, so replace those with valid characters, ex. :-

@ can be replaced with %40
+ can be replaced with %2B

something like : https://username%40xyz.com@dev.azure.com/project-name/apps/_git/library/

Effing hell this was hard to spot, why do they generate a url that messes up pushes? — Mojimi, Aug 05 '19 at 17:06
Alternatively if you don't want to do as like given above (**HTTPS** way of cloning- which is mostly used), You can try this **SSH** thing as well ::: https://learn.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops&tabs=current-page , I've tried it recently which will work either way.. — whoami - fakeFaceTrueSoul, Feb 25 '20 at 20:58
In my case I just generated the credentials and used the generated password and it worked for me. — Touseef Zaki, May 23 '23 at 10:26

score 25 · Accepted Answer · edited May 06 '19 at 10:15

25

I had the same problem with my site and it turned out the issue is with the site url: the automatically generated remote url was: https://user@site.scm.azurewebsites.net/site.git

On the other hand the portal showed: https://user@site.scm.azurewebsites.net:443/site.git

After updating the remote url in git with the following command:

git remote set-url azure
https://<user>@<site>.scm.azurewebsites.net/<site>.git
https://<user>@<site>.scm.azurewebsites.net:443/<site>.git

things started working as expected.

The morale of the story: check the deployment url as well as the password.

edited May 06 '19 at 10:15

codepleb

10,086
14
69
111

answered Aug 27 '16 at 22:52

vizmi

1,774
17
15

2

Are you sure that was 433 and not 443? – Tim Abell Nov 14 '18 at 14:35
I had to change out our Orgs name for my user name and then generate an alias and it worked fine. – dustbuster May 10 '19 at 14:27

score 14 · Answer 3 · edited Dec 10 '18 at 03:34

14

Accepted answer did not work for me but this worked.

Check your set Azure URL with

git config --get remote.<azure-remote-name>.url

Reset azure url with following command

git remote set-url <azure-remote-name>
https://<user>@<sitename>[_<slotName>].scm.azurewebsites.net:443/<site>.git

Try pushing your code using
```
git push <azure-remote-name>
```
It will open windows authentication screen which says to enter credential to connect to https://<user>@<sitename>[_<slotName>].scm.azurewebsites.net/<site>.git
Cancel this window. It will prompt the basic credential window which says to enter credential to connect to https://<user>@<sitename>[_<slotName>].scm.azurewebsites.net:433/<site>.git

Enter in your credential and it works.

edited Dec 10 '18 at 03:34

Dai

141,631
28
261
374

answered May 15 '17 at 01:55

raga

899
10
14

1

same here. thanks for sharing! yours is the only solutions that works for me – Bo Chen May 18 '17 at 01:31
To add: the end of the generated url said ...:443/.project.git, but pushing only seems to work with ....443/.git – Peanut Jan 05 '18 at 00:13
worked for me, make sure you cancel the credential window, and enter in the password in the terminal – dgamma3 Oct 16 '18 at 08:04
Thanks! For some reason, this popup does not appear when pushing from within Visual Studio. – Inrego Feb 20 '23 at 08:41
error: invalid key: https://dev.azure.com ... – Paul McCarthy Apr 21 '23 at 10:04

score 8 · Answer 4 · edited Jan 04 '22 at 20:10

8

Click on Generate Credentials and then copy the password and paste it.

It works.

edited Jan 04 '22 at 20:10

cigien

57,834
11
73
112

answered Jan 04 '22 at 19:42

Swapnil Nikale

81
1
2

worked thanks, simple and clear explanation – Farkhod Abdukodirov Jul 10 '23 at 13:25

score 6 · Answer 5 · edited Jun 20 '20 at 09:12

Since azure does not support ssh you will have to use your password at least once (in some cases you will not be prompt for password next time)

Here is an article describe how to set it up

https://azure.microsoft.com/en-us/documentation/articles/web-sites-publish-source-control/

And here is how to set up git with Azure: http://weblogs.asp.net/shijuvarghese/building-and-deploying-windows-azure-web-sites-using-git-and-github-for-windows

Here are the steps that you followed

If this is your first time setting up a repository in Azure, you need to create login credentials for it.

You will use them to log into the Azure repository and push changes from your local Git repository. From your web app's blade, click Settings > Deployment credentials, then configure your deployment username and password.

When you're done, click OK.

Now do this:

score 6 · Answer 6 · answered Nov 17 '16 at 05:07

6

I had the same problem when try to git clone https://<username>@praat.scm.azurewebsites.net:443/<repo-name>.git . I solved the problem by removing the port.

So your new url should not have the port 443.

answered Nov 17 '16 at 05:07

Joseph

5,793
4
34
41

Nilay Vishwakarma · Answer 7 · 2020-03-16T10:13:46.743

4

None of the above solution worked for me.

The reason why the same error was observed in my deployment was because my password contained a character "@".

This malformed the Git clone url for my Azure web app. When I changed my password by removing @, it solved this issue. You can change @ to %40 in your connection string as well.

edited Mar 16 '20 at 10:13

answered Sep 11 '18 at 08:48

Nilay Vishwakarma

3,105
1
27
48

score 4 · Answer 8 · answered Dec 30 '21 at 06:08

4

Login into Azure Dev Ops portal.
Go to Project you wish to clone.
Select Repo from left menu.
Click on Clone from right top corner.
Click Generate Git Credential
Enter given username & password where you are cloning repository.
you are done!

answered Dec 30 '21 at 06:08

Vikas Srivastava

51
1

score 3 · Answer 9 · answered Apr 11 '21 at 16:58

3

Current Azure Structure for adding credential

Use the highlighted user, password, confirm password section to create an user credential. Use this to proceed where you were stuck.

answered Apr 11 '21 at 16:58

d1p3

39
1

score 1 · Answer 10 · answered Jan 17 '16 at 16:50

Assuming you're entering the correct password each time, it might be a delay/propagation issue.

You can also use your Site-Level credentials as detailed on this wiki page. You can get these by downloading your publishing credentials in the Portal via the "Get Publish Profile" option on your main WebApp bar. The user name / password can then be found in the yourapp.PublishSettings file and will look something like userName="$yourapp" userPWD="ABC123". This is only mentioned as a workaround if your User-Level credentials are not working (which they should be if they are correct).

score 1 · Answer 11 · edited May 04 '19 at 13:00

1

I had a similar problem where the automatically generated git clone url was:

https://group-admin-account-username@dev.azure.com/site.git

So instead I had to replace this with my own account username

https://my-username@dev.azure.com/site.git

This then prompted me for the password for my account correctly:

git clone https://my-username@dev.azure.com/site.git

edited May 04 '19 at 13:00

Zoe

27,060
21
118
148

answered Nov 28 '18 at 22:01

Thomas M

319
2
6

score 1 · Answer 12 · answered Mar 04 '19 at 05:57

What worked for me is I created personal access token. Click username in top right corner > Security > Select Personal Access token from left pane > New Token. Provide token name and scope for your token and Click create. Save that token and use it as password.

score 1 · Answer 13 · answered Apr 25 '21 at 19:01

1

I had to do it this way

Generate Git Credentials
git remote add origin https://username:password@dev.azure.com/xxx/_git/xxx
git add.
git commit -m init
push -u origin --all

answered Apr 25 '21 at 19:01

Abdullah Tahan

1,963
17
28

score 1 · Answer 14 · answered Sep 15 '21 at 16:29

I got this error in Visual studio because I used the sync feature when the branch hadn't been created in 'https://dev.azure.com/foo/bar' yet.

Instead of doing a sync, I did a push & then it prompted me for my credentials. After that it worked fine.

Hopefully this helps someone.

axelio · Answer 15 · 2022-01-11T10:51:06.130

1

Adding token before dev.azure in URL settings worked for me. I am using SourceTree.

https://token@dev.azure.com/org/_git/repo

edited Jan 11 '22 at 10:51

answered Jan 05 '22 at 11:23

axelio

159
4

Where do you get this token? – Mateus Felipe Mar 16 '22 at 12:38
1

I have issued mine here: https://dev.azure.com/MY_ORGANIZATION/_usersSettings/tokens – axelio Mar 16 '22 at 13:56

score 1 · Answer 16 · answered Feb 22 '23 at 07:55

Go to Control Panel\All Control Panel Items\Credential Manager and click Add a Generic Credential and add URL LINK only Domain and add user name & password Finished.

git add . git commit -m "init" git remote add origin YourUrlRepo git push -u origin -all

score 0 · Answer 17 · answered Jan 18 '16 at 07:54

0

A straight forward method to get this over with is to Download/Get Publish profile (make sure you refresh the portal page) from main toolbar and use the password given in the .publishsettings file.

answered Jan 18 '16 at 07:54

Brij Raj Singh - MSFT

4,903
7
36
55

score 0 · Answer 18 · answered Aug 26 '17 at 18:44

For me it was a matter of cloning the project with the remote url and cancelling the windows security prompt. Afterwards, it'll ask you for the password. Once you're able to clone it, you can push it successfully.

Moral of the story: Clone it first before pushing.

score 0 · Answer 19 · answered Jun 27 '18 at 17:48

0

On mine, the password was never created when I set the deployment user from the cli. I had to go to the web app, app services, for the app, then set the deployment credentials

answered Jun 27 '18 at 17:48

kztd

3,121
1
20
18

score 0 · Answer 20 · answered Nov 18 '18 at 20:42

0

Go to the Security Tab >> Personal Access Tokens >> New Toke >> Give it Full Access >> Note the Access token as you will use it as your password

answered Nov 18 '18 at 20:42

iamgilwell

61
2
2

score 0 · Answer 21 · answered May 04 '19 at 09:06

this may help: with my first webapp, i had to go to Deployment Center, Deployment Credentials. And then use either the App Credentials or create User Credentials. After this, delete the cached credentials on the local machine (windows: Control Panel\User Accounts\Credential Manager). run "git push webapp master:master" again, enter either of the Deployment Credentials. That worked.

score 0 · Answer 22 · answered Oct 15 '19 at 21:24

In my case none of the above methods solved my issue (but they directed me to find out where I'm going wrong)

I tried both auto generated App credentials and my custom created user credentials, and every time I was getting authentication failed message.

The description on the credentials page was advising me to have the username in the following format:
<app-name>\<username>

This was why authentication failed. As soon as I put my username without the <app-name> prefix the authentication passed and everything worked smoothly.

Hope this information helps

score 0 · Answer 23 · answered Dec 04 '19 at 05:21

0

Navigate to the Deployment Center >> Deployment Credentials, there will be application credentials for local git. Use the username and password there will work.

answered Dec 04 '19 at 05:21

Gloria

1

score 0 · Answer 24 · answered May 23 '20 at 12:53

0

Using SSH instead of HTTPS worked for me after adding my SSH key

answered May 23 '20 at 12:53

charlchad

3,381
1
16
9

score 0 · Answer 25 · answered Jan 26 '21 at 20:15

0

Some of the above brought me close, such as the post by @Nilay Vishwakarma but I finally found the cause of my authentication issue to be that my password contained a '$' followed by a '..u7' which I eventually noticed in powershell was highlighted yellow when I typed.

I thus assumed it could be the CLi has an issue with this character in passwords (even though it wasn't mentioned as a reserved character in this tutorial).

I re-ran the 'az webapp deployment user set --user-name [user] --password [pwd]' command with a revised password without the '$' and was able to then enter my credentials and authenticate.

answered Jan 26 '21 at 20:15

Donal

31
4

Having a `$` at the begining of the password could cause the same issue, but I don't thing that this was the issue of the author of the question – phoenixstudio Jan 26 '21 at 20:59
Thanks - I get that but the authentication error message was the same, hence how I ended up here. It appears from other comments that there are various issues which will result in the same error, so since the password I entered was not accepted due to the '...$...' I considered it relevant. – Donal Jan 28 '21 at 11:59

score 0 · Answer 26 · answered Jan 31 '21 at 20:00

Using Mac I had the same issue. Using Git Credential manager worked.

Installed GCM using brew https://github.com/microsoft/Git-Credential-Manager-Core
Connected git to remote Azure Repo
On git push, pop up requested username and password
All connected.

Don't be surprised when you see PAT (Personal Access Token) in you settings.

"Once authenticated, the credential manager creates and caches a personal access token for future connections to the repo. Git commands that connect to this account won't prompt for user credentials until the token expires. A token can be revoked through Azure Repos."

Below link should help

https://learn.microsoft.com/en-us/azure/devops/repos/git/set-up-credential-managers?view=azure-devops

score 0 · Answer 27 · answered Jun 24 '21 at 14:01

If you are using Sourcetree and you tried all of the answers here and nothing works.

try cloning your project again using this url structure as source:

https://<username>:<password>@dev.azure.com/project-name/apps/_git/library/

username and password comes from the Generate Git Credentials button when you clone your branch.

score 0 · Answer 28 · answered Oct 13 '21 at 13:38

If you unable to clone the projects/repos,

Check proxy settings or VPN if provided
Check repository path access
Check your access or password expiry

If you are facing login issue,

Generate PAT (Personal Access token) for respective version control system like Git, Azure etc.
If PAT fails, create alternate credentials
If this both are right and still you are unable to access then
1. Goto your repository click on Clone button, there you can find Generate Credentials button. Try to login with those newly generated credentials.

Check for all above options first. If you are following everything and still facing issues then try to take help from colleagues/team leader/ manager or client.

score 0 · Answer 29 · answered May 20 '22 at 09:00

0

I suddenly had the same problem. It turned out to be a problem with my local station and the Internet adapter being rejected leading to not authenticated. Disabling IPV6 solved the problem for me: See https://stackoverflow.com/a/69712045/7302498

answered May 20 '22 at 09:00

Astrophage

1,231
1
12
38

canerkaseler · Answer 30 · 2022-08-31T18:21:57.847

0

I had a same problem because of saved login info in Macbook.

I entered Key Chain Access App of Mac.
Then, I found login info under login, opened it.
I updated password with my Credential Password of Azure Repo. (Click "Generate Git Credentials")
Done! Now, I can pull my branch in SourceTree.

edited Aug 31 '22 at 18:21

answered Aug 31 '22 at 18:09

canerkaseler

6,204
45
38

score 0 · Answer 31 · answered Jan 25 '23 at 21:07

0

In my case, I had to provide the Personal Access Token (PAT) that was created when I created a new Azure Organization, instead of any password. This PAT needs to be saved by you since it will not be available later after you close the PAT screen.

I had forgotten my PAT and had to regenerate it and provide it for the Git login, for this issue to resolve.

answered Jan 25 '23 at 21:07

ManojDexter

21
2

As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jan 28 '23 at 09:27

score -1 · Answer 32 · answered Sep 14 '16 at 20:10

-1

In my case it looks like azure server is slowing down.

Git deployment

git push azure master

fatal: Authentication failed for

FTP deployment

Authentification - OK upload speed 1-10K

answered Sep 14 '16 at 20:10

citleon

378
2
7

Authentication failed for Azure Git

32 Answers32

Now do this:

Linked

Related