@@ -226,7 +226,16 @@ Afterwards, you can follow these steps...
226226 1 . Walk through the wizard, but make sure to pick the same resource group as the environment you plan to test.
2272273 . After creation, navigate to the Identity slice, which is under the Settings group, of your new load test.
228228 1 . Turn the Status to On under the System assigned tab and click Save.
229- 4 . <TBD key vault >
229+ 4 . Navigate to the TI key vault in the same resource group as the load test.
230+ 1 . Navigate to the Secrets slice, under the Objects group, and click Generate/Import.
231+ 2 . Provide the name ` trusted-intermediary-valid-token-jwt ` .
232+ 3 . The secret value should be a newly created JWT that won't expire in a long time using the
233+ ` organization-trusted-intermediary-private-key-<environment>.pem ` private key in Keybase as the signing key.
234+ 4 . Click Create.
235+ 5 . Drill into the latest version of this secret, and click the copy to clipboard button in the Secret Identifier
236+ textbox. We will be using this later during the creation of the actual load test.
237+ 6 . Navigate to the Access policies slice, and click Create. Select Get and List for Secrets for the permissions and
238+ the name of the previously created load test as the principal.
2302395 . Navigate to the Tests slice, which is under the Tests group, of the previously created load test and click Create and then Upload a script to start
231240 walking through the wizard.
232241 1 . Under the Test plan tab...
@@ -236,7 +245,11 @@ Afterwards, you can follow these steps...
236245 FHIR files. You can inspect the ` locustfile.py ` file to find out which data files are used. As of this
237246 writing, that is ` 002_ORM_O01_short.fhir ` and ` 001_ORU_R01_short.fhir ` .
238247 2 . Under the Parameters tab, add a secret with ` trusted-intermediary-valid-token-jwt ` as the name. The Value is the
239- secret URL referenced previously when you added the JWT to the key vault.
248+ secret URL referenced previously when you added the secret JWT to the key vault. Before pasting the secret,
249+ remove the hexadecimal version from the end of the URL. E.g.
250+ ` https://<key-vault>.vault.azure.net/secrets/trusted-intermediary-valid-token-jwt/cf7eb05481c449878f2afe6b51464fd5 `
251+ becomes ` https://<key-vault>.vault.azure.net/secrets/trusted-intermediary-valid-token-jwt/ ` . We always want to
252+ reference the last version, and we can do so by omitting the specific version.
240253 3 . Under the Load tab, configure how much load you want. You also need to provide the URL of the application you
241254 want to load test.
242255 4 . Under the Test criteria tab, fill in any client-side metrics that you want to evaluate at the end of the load
0 commit comments