[Bug]: Build Fails in 8.1 with 401 Unauthorized Error for Key Vault Access

[Gummi007]

AL-Go version

8.1

Describe the issue

After updating to AL-Go version 8.1, the build fails with the following error:

##[error]Unexpected error when running action. Error Message: Exception calling "GetResult" with "0" argument(s): "Response status code does not indicate success: 401 (Unauthorized).", StackTrace: at DownloadFileLow, C:\ProgramData\BcContainerHelper\6.1.10\BcContainerHelper\HelperFunctions.ps1: line 1046 <- at Set-BcContainerKeyVaultAadAppAndCertificate, ...

The same build works in v8.0 here is atleast one thing I observed, when reading the settings there is a difference between versions

8.0:
"keyVaultCertificateUrlSecretName": ""
8.1:
"keyVaultCertificateUrlSecretName": "keyVaultCertificateUrl"

Expected behavior

The AL-Go build should complete successfully in version 8.1, as it did in 8.0.

Steps to reproduce

1. Update AL-Go to version 8.1
2. Create a PR that starts the Pull Request Build action

Additional context (logs, screenshots, etc.)

No response

[mazhelez]

Hi @Gummi007 and thank you for reporting this!

Is there a way to include a bit more logs? Are you using a key vault integration in your build?

You can try and set keyVaultCertificateUrlSecretName setting to "", to see if that helps.

[Gummi007]

@mazhelez I'll attach the complete logs. I'm not quite sure if we are using a key vault integration, we have the AZURE_CREDENTIALS secret set but no other secrets set for key vault.

setting the keyVaultCertificateUrlSecretName to "" seems to work as a workaround but the build works without setting it in v8.0.

[mazhelez]

You seem to have a secret called keyVaultCertificateUrl which is used for key vault integration.

In 8.0 that functionality was not working. In 8.1 it is supposed to work, but in your case the authentication to the key vault fails. I assume you don't use key vault integration, so I suggest you simply remove the secret.

[Gummi007]

You are correct we were using the key vault integration that stopped working some time ago which I guess is now starting to work but we have some expired values.