I am trying to Record script with jmeter Test Script recorder.
I added RootCA certificate to browser by following the steps (http://jmeter.apache.org/usermanual/jmeter_proxy_step_by_step.pdf)
But still when i Start to record its again giving me alert to install Root CA certificate,
Any suggestions please help.
Thanks.
If the alert you're talking about is the popup in jmeter that pops when you start recording then there's nothing you can do about it, jmeter doesn't know about your browser certificate install.
Note it's an information popup, so if you did what it advises you can ignore it
Related
In our application we are using "I am not a Robot Captcha".when we enable proxy and we access the application, the captcha is not displayed. Because of this, we are not able to proceed with our scripting in Jmeter. Is there a way to make captcha visible while using Proxy?
Most probably your issue is with HTTPS, did you add the jmeter generated certificate to accepted Authorities ?
Anyway, if it's recaptcha system you should not be able to automate it as it is made to block robots, and JMeter is a robot here.
So disable it anyway for your test.
This is my first post, and I hope you guys can help me.
What is the problem?
When I was developing my app I used an unencrypted connection (because I had no valid and trusted certificate) so it worked all the time. Now is the app almost done, and I want to use a encrypted connection. I bought a valid certificate for my server and it is working as it should be, when I go in my browser to my server it says that is has a valid and trusted certificate. But, when I change the server url in my app, I get the error: "The operation couldn’t be completed. (NSURLErrorDomain error -1012.)".
I searched the internet, but I found most of the time problems with a self-signed certificate, and they had to set allowInvalidCertificates to true. Ofcourse, I don't want to set this option to true, it has to be false. Also the pinning option is set to None, so actually I dont understand why the app can't connect to my server while it is using a valid certificate.
I hope some of you can help me!
[update]
When I change the allowInvalidCertificates to true, it works. So I think it has something to do with the verification of the certificate. When I'm browsing in the simulator with safari to the server-url it just opens as it should. No warnings or errors.
Thanks, Joey
Yes, got it!
First I checked the status of my ssl-server at: http://www.sslshopper.com/ssl-checker.html
Then I saw that there was something wrong. The certificate was not trusted by all major web browsers.. So, I had to add the CA-bundle on my server en then tada! All tests passed.
I checked directly my connection with the app and yes, it worked immediately :)
Maybe some of you guys have the same situation, and this could be your answer :) Good luck!
Cheers, Joey
I am having great issues trying to debug a page on a web application used internally on an intranet. When entering the page the "Security Information" Pop Up Box appears. The whole application is running under https.
To try and debug the issue, I have used Fiddler, and looked at the urls for every component, javascript, css, images, and user control components. Everything I have seen from Fiddler shows that the urls start with required https!
So, I am completely confused why this message should be shown - it appears everything the page is posted back.
Does anyone have any idea why this should be happening and/or have another tool that could help me?
Thanks
I'm pretty sure that what you are seeing is the result of a self-signed certificate. If a certificate you're using isn't trusted by a known certificate authority (Verisign or a similar company) your web browser can't verify that it comes from a trusted source.
Also, look at what the error is saying, because it usually tells you which part of the security verification failed.
I have a IIS website with a security certificate setup using SelfSSL (part of the IIS Resources toolkit). The certificate appears valid when I view it in ISS and it works fine for IE, Safari and Google Chrome. However, in Firefox 3 it does not consider the certificate valid and therefore shows a certificate warning when you view a secure page on the website.
This is only a problem because I am using Selenium to automatically test the site. I have tried using custom Firefox profiles to solve this problem and this works ok with one IIS site. But when each developer has their own site you have to keep adding exceptions to this custom profile.
I can use other browsers for the Selenium scripts, but I would rather use Firefox (the form input on IE seems to run much slower than Firefox).
I think the easiest way around this problem is to have valid certificates in the first place, hence I started using SelfSSL. Any ideas why Firefox doesn't seem to take any notice?
SelfSSL does not generate a valid certificate - it generates a self signed one. To get a valid certificate you have to buy one from a certificate authority.
If your IE, Chrome or Safari do not show a warning when visiting your secured page it means that you have added this new certificate to trusted certificates database of your account. You can do this in Firefox too - it just has a separate database. But your every user has to do this for himself.
I am maintaining a few web applications. The development and qa environments use invalid/outdated ssl-certificates.
Although it is generally a good thing, that Firefox makes me click like a dozen times to accept the certificate, this is pretty annoying.
Is there a configuration-parameter to make Firefox (and possibly IE too) accept any ssl-certificate?
EDIT: I have accepted the solution, that worked. But thanks to all the people that have advised to use self-signed certificates. I am totally aware, that the accepted solution leaves me with a gaping security hole. Nonetheless I am to lazy to change the certificate for all the applications and all the environments...
But I also advice anybody strongly to leave validation enabled!
Try Add Exception: FireFox -> Tools -> Advanced -> View Certificates -> Servers -> Add Exception.
I ran into this issue when trying to get to one of my companies intranet sites. Here is the solution I used:
enter about:config into the firefox address bar and agree to continue.
search for the preference named security.ssl.enable_ocsp_stapling.
double-click this item to change its value to false.
This will lower your security as you will be able to view sites with invalid certs. Firefox will still prompt you that the cert is invalid and you have the choice to proceed forward, so it was worth the risk for me.
Go to Tools > Options > Advanced "Tab"(?) > Encryption Tab
Click the "Validation" button, and uncheck the checkbox for checking validity
Be advised though that this is pretty unsecure as it leaves you wide open to accept any invalid certificate. I'd only do this if using the browser on an Intranet where the validity of the cert isn't a concern to you, or you aren't concerned in general.
In the current Firefox browser (v. 99.0.1) I was getting this error when looking at Web Developer Tools \ Network tab:
MOZILLA_PKIX_ERROR_SELF_SIGNED_CERT
I was trying to debug an Angular app which is served at https://localhost:4200... however the real port it's pointing to and being debugged from in Visual Studio 2022 is 44322.
I had to follow these steps to fix the issue:
Open Firefox Settings;
Look for Privacy & Security tab on the left;
Scroll down to the bottom and look for Certificates;
View Certificates;
In this window you must click Add Exception and enter the location. In my case it was:
https://localhost:44322
Click Get Certificate button;
Click Confirm Security Exception button.
After that, try reloading your page.
Instead of using invalid/outdated SSL certificates, why not use self-signed SSL certificates? Then you can add an exception in Firefox for just that site.
Using a free certificate is a better idea if your developers use Firefox 3. Firefox 3 complains loudly about self-signed certificates, and it is a major annoyance.
If you have a valid but untrusted ssl-certificates you can import it in Extras/Properties/Advanced/Encryption --> View Certificates. After Importing ist as "Servers" you have to "Edit trust" to "Trust the authenticity of this certifikate" and that' it.
I always have trouble with recording secure websites with HP VuGen and Performance Center
Create some nice new 10 year certificates and install them. The procedure is fairly easy.
Start at (1B) Generate your own CA (Certificate Authority) on this web page: Creating Certificate Authorities and self-signed SSL certificates and generate your CA Certificate and Key. Once you have these, generate your Server Certificate and Key. Create a Certificate Signing Request (CSR) and then sign the Server Key with the CA Certificate. Now install your Server Certificate and Key on the web server as usual, and import the CA Certificate into Internet Explorer's Trusted Root Certification Authority Store (used by the Flex uploader and Chrome as well) and into Firefox's Certificate Manager Authorities Store on each workstation that needs to access the server using the self-signed, CA-signed server key/certificate pair.
You now should not see any warning about using self-signed Certificates as the browsers will find the CA certificate in the Trust Store and verify the server key has been signed by this trusted certificate. Also in e-commerce applications like Magento, the Flex image uploader will now function in Firefox without the dreaded "Self-signed certificate" error message.
For a secure alternative, try the Perspectives Firefox add-on
If this link doesn't work try this one:
https://addons.mozilla.org/en-US/firefox/addon/perspectives/
The MitM Me addon will do this - but I think self-signed certificates is probably a better solution.