Tried uploading Keystore file to Testplan and Updated keystore details in System.properties file. Nothing worked.
And the test needs Auth token which is generated by sending client id and secret. I don't want to give the client id and secret in the jmx file. I will generate Auth token separately and send it in the HTTP header. This works fine in the jmeter script. But in the Azure load test portal, 403 error is occurring.
Please help for both issues and are these issues interrelated?
Hello @Prima25-1641 - Thanks for reaching out and apologies for the delay in response.
I have reached out to product team and will get back to you as soon as I can.
Thank you for your patience and cooperation while i work on this issue.
Hello @Prima25-1641 - Did the below answer help resolve your issue, if not please revert back with any questions.
and if it did, please feel free to "accept as answer" so it can be beneficial to the community.
Hello @Prima25-1641 - Thanks for reaching out and apologies for the delay in responding to you.
Try to configure clientID and secret outside jmx script and see if that helps.
Please take a look at this doc for reference: how-to-parameterize-load-tests
----UPDATE:
Looks like you are using certificates for authorization. Currently Azure Load Testing does not support certificate-based authorization. If you can generate a token using client id and secret, you can do that following the steps mentioned here
Hope this helps. and please feel free to reach out if you have any further questions.
If the above response was helpful, please feel free to "Accept as Answer" and "Upvote" the same so it can be beneficial to the community.
Is there a planned update to support this? I was previously using OctoPerf to test an MTLS-secured service and it was working fine, uploading and specifying a keystore (PFX) through system properties. It feels like this is a pretty obvious use case, and I would love to leverage azure's load test instead.
@ShanePilo-9466 - Thanks for reaching out to us and bringing this to our attention.
System properties file is not supported by Azure Load Testing at the moment and it's in our backlog and we do not have an ETA at the moment.
I have also raised an issue in GitHub repo for Product team to track and prioritize accordingly.
Thank you.
I am trying to configure load test using .yaml file (using Azure Load Testing Task) and want to use multiple certificates in KeyStore.p12 file as input to my test. By using this KeyStore.p12 file and a KeyStoreAliasReference.csv referred in jmx file, I am able to run this using jmeter where I am configuring following properties in system.properties file of jmeter. javax.net.ssl.keyStoreType=PKCS,javax.net.ssl.keyStore=KeyStore.p12,javax.net.ssl.keyStorePassword=testpassword, https.use.cached.ssl.context=false,https.keyStoreStartIndex=0,https.keyStoreEndIndex=3
Referred
https://docs.microsoft.com/en-us/azure/load-testing/reference-test-config-yaml
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/test/azure-load-testing?view=azure-devops
and tried passing above properties in yaml configuration using following but did not work.
Please suggest on how/where can these properties be specified so that certificates from KeyStore.p12 file are picked up correctly.
env: |
[ {
"name": "javax.net.ssl.keyStoreType",
"value": "PKCS12",
} and so on
]
Thanks
@Pankaj-2265 - I have provided an update for your question above. Please take a look and see if that helps answer your question. Thank you.
5 people are following this question.
