-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Webclient authentication #406
Comments
Where are you hosting your web client server? Generally you would want to keep that within a private network. |
Both my locust server and the API I am load testing are both living on AWS. The API won't be publicly exposed, but the locust interface will be so that the client can easily access it. I was hoping there was a feature like Basic Http Auth in Flask so that I can secure the Locust GUI. |
There's no reason the web interface couldn't include basic auth, but I think that's a rare use case since most people use locust internally or destroy the master when they're done with it. I would recommend putting nginx in front of your locust server, which has much better auth support and is something you could set up today rather than waiting for auth to be tested and released. |
You can also look into setting up a VPC with Amazon: https://aws.amazon.com/vpc/ |
Great! Thanks for the help Justin. I will take a look into the Nginx route, as I am already running it with nginx, though i am new to it so I wasn't aware of that feature. |
Here are the docs to get started: http://nginx.org/en/docs/http/ngx_http_auth_basic_module.html |
I am using Locust to set up load testing for a client, but one requirement I have is that the Webclient needs to be password protected so that not just anybody can go to the URL and initiate a load test. Is there any way to do this?
The text was updated successfully, but these errors were encountered: