Thank you, I missed the popup notification (imho it's easy to miss after the popup has disappeared, but it's definitely there on the Notifications tab )
I use the Surface theme and I'd like to set a selectable per-user and per-machine installation installation.
I set these: Install parameters: - Installation type: Per-machine if user is administrator, per-user otherwise - Application folder is [AI_UserProgramFiles]\product_family\product ...
thanks for the quick reply! The full path for that file is less than 100 characters long, so I think that's fine; although, in the log, I see old DOS format file names with the '~' character. Weird.
I'll send you the AI file and the full log. I'll need some time to get everything ready ...
you can use the Build Advanced Installer package task in Azure, you don't have to create an aic file manually. The task also has a command line arguments section where you can set the SetAzureKeyVaultSecret command: SetAzureKeyVaultSecret SecretEnvVarName -secret_is_env_var_name or ...
Hi Catalin,
could you confirm if this is a bug in AI or in AI-Azure integration or if we do something wrong? If it is a bug, then do you think we could expect a fix soon?
I'd like to set up our release pipeline in Azure with signing from the Key Vault and this is the only thing which blocks us.
Hello Catalin,
I tried it and unfortunately it doesn't work.
I still get "A required argument is missing: <azure_key_vault_app_client_secret>."
I tried this with AI 17.5.
I tried to circumvent the '-' issue by using SetAzureKeyVaultSecret SecretEnvVarName -secret_is_env_var_name but so far I only get an error: 'Unable to get Azure Sign token. AADSTS7000216: 'client_assertion', 'client_secret' or 'request' is required for the 'client_credentials' grant type ...
I tried this locally: ;aic SetVersion 1.2.3.4 SetAzureKeyVaultSecret -asdf- Build
There are '-' characters in the secret and it seems they cause the problem. If I remove them, the build starts (but I'll get an invalid secret key error of course). I had the same locally and in ...
Hi, I've read that Azure Key Vault is now supported. Could you point me to a tutorial about the recommended way to set it up in Azure DevOps?
I was able to sign my app locally using the "User From Azure Key Vault" option within AI. I also read about calling AzureSigntool in a task as a workaround ...