Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Azure Load Test is not recognized as a trusted resource to bypass Key Vault firewall #117

Closed
cathalmchale opened this issue Nov 4, 2022 · 11 comments
Assignees
Labels
enhancement New feature or request

Comments

@cathalmchale
Copy link

cathalmchale commented Nov 4, 2022

Describe the bug
Azure Load Test can access Key Vault, only if setup to allow access from All public networks. If Key Vault chooses to limit public access to specific vnets, then Load Test can no longer fetch secrets. This is true even when the "allow trusted Microsoft services" option is selected:

image

To Reproduce
Steps to reproduce the behavior:

  1. Setup two Key Vault instances - one that allows access to all public networks and one that limits access to specific vnets.
  2. Add an access policy to both Key Vault instances to allow Secret Get - use the same managed identity in both cases.
  3. Create a Load Testing instance. Configure the Identity as User managed and set the identity to the same added to the Key Vault access policy.
  4. Create a test that injects a secret. I set the value to the URL of the more private Key Vault secret.
  5. Run the test - observe that when leave the value pointiing to the more private Key Vault, it fails to start the test, but when change the value to the more public Key Vault it runs successfully.

Expected behavior
Should be able to access the more private Key Vault - either by being able to specify a vnet when creating the Load Testing instance, or by having Azure Load Testing be a "trusted Microsoft resource" that can still gain access to the Key Vault.

Screenshots
Private vs Public Key Vault. As in steps to repro, the access policies in both Key Vaults are the same, using the same identity. Then the same Load Test is used to trigger a success and a failure, varying only the URL of the Key Vault secret.

image

The more private Key Vault looks like this:

image

image

Additional context
Have tried with both User managed and System managed identities.

AB#1665865

@Sachid26
Copy link
Contributor

Hi @cathalmchale ..currently this is not supported by the service, and we have added this to our backlog. We will report back once we implement this.

@karkavi980
Copy link

karkavi980 commented Mar 8, 2023

Hi @Sachid26 - any update on this feature? Is there any work around?

@karkavi980
Copy link

Hi - Any update on this feature? Is there any work around?

@markditianquin
Copy link

Bump... Any update?

3 similar comments
@denhsu
Copy link

denhsu commented Aug 4, 2023

Bump... Any update?

@ffurrer2
Copy link

ffurrer2 commented Sep 8, 2023

Bump... Any update?

@BlauerPulli
Copy link

Bump... Any update?

@sulabh-msft
Copy link

Azure load testing service now supporting Azure keyvaults behind a firewall or a private virtual network.

https://learn.microsoft.com/en-nz/azure/load-testing/how-to-parameterize-load-tests#create-a-secret-in-azure-key-vault

If you restricted access to your Azure key vault by a firewall or virtual networking, follow these steps to grant access to trusted Azure services.

@sulabh-msft
Copy link

@Nagarjuna-Vipparthi Can we close the issue now?

@karkavi980
Copy link

karkavi980 commented Apr 8, 2024 via email

@Nagarjuna-Vipparthi
Copy link
Collaborator

Requested feature is now supported. Closing the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

10 participants