Closed WouterSlob closed 2 years ago
Hi @WouterSlob .. thanks for reporting this and the detailed steps that you have done to enable authentication scenario. We are looking into this issue and will get back with some information soon.
@kusweta Can you please check this?
Hi @WouterSlob, we have fixed the issue with GetSecret. Could you please try running your test now and confirm if this is working for you?
Hi @ninallam, do I have to recreate my Azure Load Testing resource?
Because at the moment tests are not running at all anymore. I've already tried to create a new test without __GetSecret and that one stays in status "Executing", but no requests are send at all. After cancelling the test status stays in "Cancelling", although I got a "Test run stopped." confirmation in the portal.
@issacnitin Can you please check this?
@ninallam / @issacnitin : any update on this? Already tried re-creating the resource and that did not work. Also tests in another resource that used to work are not starting anymore.
Hi @WouterSlob could you please check if you are still facing this issue? If yes, which region are you running the tests in?
I've created #33 for the problems with execution. I'll try to test __GetSecret in a different way.
__GetSecret works now. Thnx!
I've tried to use KeyVault icw Azure Load Testing, following the steps described at https://docs.microsoft.com/en-us/azure/load-testing/how-to-parameterize-load-tests#secrets, but the __GetSecret seems not to be working.
What I did was:
After running my Test I found the string "${__GetSecret(ClientId)}" iso the secret in the log files of the webserver.
So it looks like __GetSecret did not work.
Searching the internet for "__GetSecret " also seem to return only the Azure Load Testing page. Is there something special needed to get this working?
AB#1455476