Skip to content

Commit 283e553

Browse files
committed
Added info about no need to update JMeter
1 parent 21f1a41 commit 283e553

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/load-testing/how-to-test-secured-endpoints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -128,7 +128,7 @@ When you now run your load test, the JMeter script can retrieve the secret infor
128128

129129
In this scenario, the application endpoint requires that you use a client certificate to authenticate. Azure Load Testing supports Public Key Certificate Standard #12 (PKCS12) type of certificates. You can use only one client certificate in a load test.
130130

131-
To avoid storing, and disclosing, the client certificate alongside the JMeter script, Azure Load Testing uses Azure Key Vault to store the certificate. When you run the load test, Azure Load Testing passes the certificate to JMeter, which uses it to authenticate with the application endpoint.
131+
To avoid storing, and disclosing, the client certificate alongside the JMeter script, Azure Load Testing uses Azure Key Vault to store the certificate. When you run the load test, Azure Load Testing passes the certificate to JMeter, which uses it to authenticate with the application endpoint. You don't have to update the JMeter script to use the client certificate.
132132

133133
The following diagram shows how to use a client certificate to authenticate with an application endpoint in your load test.
134134

0 commit comments

Comments
 (0)