0

I am following this article to create a simple app service wiht container image pulled from an ACR: https://learn.microsoft.com/en-us/azure/app-service/tutorial-custom-container?tabs=azure-cli&pivots=container-linux.

Everything works fine, except the last webhook part where the app service will be notified in case there is an updated image available. The web hook call from ACR to app service always returning 401 unauthorized. Same behavior from fiddler call in case I try to access the web hook endpoint directly using a POST ping command. It seems the basic auth to access the SCM of the web app is not working.

Steps:

  1. Create an acr and pull a default image from MCR into the ACR to use later in the web app and enable admin access/keys for the ACR. 2: Create a linux based container web app pointing to above ACR using admin key & use the image pulled earlier.

At this point the web app is up in a few seconds after the initial pull.

  1. Now enable continuous integration in the web app, that will create a webhook in the ACR automatically.
  2. Go back to the webhook of the ACR & try ping test, which fails with 401 unauthorized.
  3. Additionally take the web app's WebHook URL & try accessing the same using a CURL/postman/fiddler POST call, same failure with 401 unauthorized.
  4. Try pushing the same image to ACR with --force flag to rigger the webhook, then check logs & see the same 401 error in the webhook

What am I missing here?

enter image description here

enter image description here

SanjayD
  • 156
  • 4
  • 12

2 Answers2

0

In this step make sure you are copying the password of ACR correctly.

az acr credential show --resource-group msdocs-custom-container-tutorial --name valleysili36

enter image description here

And make sure you have sufficient role assigned, to create and assign the role with the command below:-

az role assignment create --assignee $principalId --scope $registryId --role "AcrPull"

Its necessary to add AcrPull role to a "Managed Identity or Service Principal".

In addition to this, You can attempt to regenerate the admin keys and access for the ACR and then build the webhook with the new keys. Additionally, confirm that the webhook URL produced by the az webapp deployment container config command is accurate and that the registry name and resource group you provide when creating the webhook are both valid.

You can refer this steps and enable container logging.

Try to pass custom authorization Header in ACR webhook Configure settings by referring to the paylod here

enter image description here

Check the Azure Web app logs and validate if the Web app is running successfully, If Web app runs successfully the Webhook ping will be successful.

enter image description here

Refer this answer by Jahnavi for more details.

SiddheshDesai
  • 3,668
  • 1
  • 2
  • 11
  • Thanks for the details. But we are using MSI to communicate between app & acr, so admin credentials are not enabled. Also now as I see the problem is not acr itself it seems. If we just add any app service with any public container image (from MCR or dockerhub), and then if we pick up the WebHook url & try a POST ping message (to the same kusto url (which uses basic auth), the reply from the hook endpoint is 401. So at the end its the app service web hook url (which is nothing but a basic auth backdoor to kudo, is not working for us) – SanjayD Aug 03 '23 at 06:27
0

Ran into this issue myself recently. It turned out that we had disabled the "Basic Auth Publishing Credentials" setting for the App Service. Since the webhook uses basic auth for authentication, this needs to be enabled for it to work. Once we enabled this setting, the webhook started to work as expected.

App Service Settings Screenshot

Jeremy Caney
  • 7,102
  • 69
  • 48
  • 77
oystehei
  • 1
  • 1