Question on create_account.py

[grandamp]

Hi! Before opening a new issue, please make sure it has not already been
reported.

Once you are sure the issue is valid, please fill out the details below.

Thanks!

Steps to reproduce the issue (please be as specific as possible)

Please forgive me for creating an Issue, but I've been pulling my hair out trying to test another rest service that is strictly TLS 1.2 (and may be a consideration for this IdP).

When using Locust to test another rest service that is strictly TLS 1.2, I experience a high error rate (Locust Empty Response). Has this been encountered using locust to test this service, when this service is limited to TLS 1.2 on the web servers?

@konklone I have additional information to share, but, related to a service in a closed repo.

Thanks in advance!

[sverch]

Hi @grandamp, thanks for the issue.

The create_account.py script was written specifically to test the application in this repository, so the scripts provided here won't work for any other application without some customization.

I would recommend reading the Locust documentation here: http://docs.locust.io/en/latest/ if you're looking for more information about how to write a Locust load test for your application. Locust should by default work with TLS 1.2, but if you find it doesn't you may need to upgrade your locust and python versions.

[grandamp]

Hi @sverch,

I am not attempting to use create_account.py. I was asking if your locust tests included testing this service when it is served with TLS 1.2 only? If so, did you experience a lot of "empty" failures due to TLS negotiation problems?

[sverch]

Ah, sorry I misunderstood your question. I don't know if we've ever configured our app to run TLS 1.2 only.

This may be a good place to start: https://security.stackexchange.com/questions/127984/what-website-accepts-only-tls-1-2-so-i-can-verify-client-capability. I ran a locust test against one of the sites they claim only supports TLS 1.2 and it worked for me on locust version 0.7.5. If it fails for you, then it may be related to your usage of locust (and not a server issue), and that might help you narrow it down. Hope that helps!

I'll close this out for now, since it's not related to a bug in this application specifically.