How to fix issue "Error code: SEC_ERROR_UNKNOWN_ISSUER" with JMeter and Firefox - jmeter-5.0

I have installed the JMeter and Firefox. when I'm recording the script it is throwing an Error code: SEC_ERROR_UNKNOWN_ISSUER and I have installed the certificate in both Firefox as well as in the system
I"m using windows Machine and working on JMeter tool. Freshly installed JMeter and Firefox and installed the certificate in both machine as well as on the browser but event then it is throwing an Error code: SEC_ERROR_UNKNOWN_ISSUER

There is no need to install JMeter Certificate in Windows system storage, just in browser.
So, check that you have done every step:
Remove all old certificates from browser and windows.
Press Start record in HTTP(S) Test Script Recorder.
Install new just created certificate in your browser (ApacheJMeterTemporaryRootCA.crt located in your JMeter bin directory).
Do actions with your web application to record requests.
How to remove old and add new certificates in Firefox:
Start Firefox
Open menu
Options
Privacy & Security
View Cerificates
Ensure there are no certificates with names "_DO NOT INSTALL..", "DO NOT INSTALL..", "JMETER.." and other related to JMeter cerificates, or Delete them if they present.
Click Import.
Navigate to your JMeter bin dir and choose ApacheJMeterTemporaryRootCA.crt file.
Check Trust this CA to identify websites.
Press Ok

Related

How to set a custom download path in Chromium in Truclient protocol of Loadrunner

I am trying to record a UI in Truclient protocol using its Chromium extension. As part of my workflow, I am downloading a file by clicking a button on UI. While replaying my script the downloaded file is saved in the default download path of Chrome. I can see the settings of Truclient Chromium browser where the path is editable. But as soon as the "develop" mode is exit, the path resets to the old default (which is also the default in system).
I want to control where my file should be saved after download on the load generator. Any advise is appreciated!
notes -
I am looking for solutions only specific to Chromium and not for IE or Truclient Browser as my UI is only compatible with Chrome.
LR version - 12.6x
Currently as I known, TruClient still do not support customize the download path in Chromium. You could try to switch to TruClientBrowser which is based on Firefox.
Open TruClientBrowser
Navigate to about:config
Add key value as:
Replay and save your script before close the browser
Reopen the script and test the download path again
TC Chrome uses the default download path.
For Windows, this is usually:
C:\userName\Downloads
and can be changed using
Ctrl+E (Open File Explorer) -> Right Click on Downloads -> Click Location -> Change the Path

ApacheJMeterTemporaryRootCA.crt not found in BIN folder

I have not been able to see the ApacheJMeterTemporaryRootCA.crt file in the bin folder. I am running jmeter 5.2.1. I need to sort this so I can be able to add certificated to my API calls to the server. Please any help or pointing me to the right direction would be a life saver.
Or if anyone has an easier way I can attach certificates to each call to the server that might also work. I am running out of options.
Thanks.
JMeter by default out of the box doesn't come with this certificate in any of the versions until you actually start recording. In case you have migrated from a different machine/environment I would suggest below in the box where you are not able to see the certificate.
Add a Test Script Recorder, select Target controller to itself and click on Start. Once you start the recording and the pop-up for the certificate appears, refresh bin directory and you will be able to see the certificate.
In my case I run this file and then ApacheJMeterTemporaryRootCA.crt appear in bin folder (apache-jmeter-5.5 version)
apache-jmeter-5.5\apache-jmeter-5.5\extras\proxycert.cmd

Preventing Chrome Extension Uninstallation?

My company has Chrome with our custom extension running on windows machines.
Our goal is to launch chrome locally on our machines with our extension running at all times. Our users are constantly looking to uninstall our extension.
Our current approach is to utilize the ExtensionInstallForceList registry key. This sort of works:
Right now, one can still click into C:\WM_0.0 and delete the folder. Once the folder is deleted, this extension is gone.
So we tried the following:
Create a windows account "Client"
Assign "Client" to "Client Group"
Change the permission C:\WM_0.0 to Deny Write
Log out and login to the machine again as Client.
Once I login to my windows machine as Client, I can no longer load my extension:
I tried to change the folder's permission to Full Control for both Users and Client Group but I am still seeing this error in Chrome.
1. How can I load this extension successfully given my current set of circumstances?
2. Is there a better way to do this?

How to install unpacked extension in firefox & chrome?

i have created extension by using crossrider they gave me xpi & crx file which i extracted and want to install manually by copying data to the browser's extension path.
I've read & tried many posts regarding this but they are not helpful because i think some posts are old & not able to find target paths & registry.
like in many posts they say create the following key in the registry here
32-bit Windows: HKEY_LOCAL_MACHINE\Software\Google\Chrome\Extensions
but i couldn't find that on my windows registry & i am using 32bit.
i want something like i copy my extension data to the browser's extension directory & inject some registry value thats all. if it possible then How?
For firefox just add the xpi or unpacked folder to the profile folder. No need for registry so its cross platform.
It can't be automatic as spyware would be all over that. After placing xpi in the extensions folder of the profile, on next startup of Firefox it will prompt saying it found an unauthorized by user add-on, and gives user a chance to enable it, or keep it disabled.
If you want to do it without startup, just launch the file path to the xpi or unpacked folder (if unpacked folder doesnt work, then point it to the install.rdf) in the browser, user will be prompted if they want to install.
There are some registry options though: Install Firefox extension using Windows registry
In Chrome, it's no longer possible to add an extension programmatically on Windows unless the extension is actually published in the Store.
This is for security reasons: previous registry-based (and otherwise) methods were open to malware abuse.
If your extension is published in the store, you can add it semi-automatically via registry. The user will still be asked whether to enable it on the next load.
You can also install extensions silently using Enterprise policy (only if the machine is part of a Windows domain and you have admin rights on the domain policy), on other OSes, or load it unpacked for testing with the --load-extension command line switch (will not persist after Chrome is restarted).
In Chrome go to
chrome://extensions
Enable Developer Mode at the top and click on the button to load an extracted extension.

Installing firefox extension for all users [system wide installation]

I have written a Firefox extension which is packed as an .xpi file. I want to install this extension for all users. Somewhere I found that we can achieve this by putting the file in the Mozilla\Extensions folder, then the extension will be available to all users.
But the problem is after installing the extension, on first launch of Firefox
for an administrator, a pop-up tab will appear to ask whether to enable or disable the extension, but
for the non-admin user, no pop-up will be there and the extension will be disabled for them initially.
Is it possible to notify every user by launching a pop-up tab when they start the browser the first time after installation?
Just to provide the old answer, which no longer worked flawlessly:
If you want to do a silent administrative install [...]:
uncompress the .xpi file yourself (as a ZIP file) to an appropriately named (extension's ID) folder. On Linux/Unix platforms you can use a helper script to determine extension IDs in an automated fashion.
Put this directory into the browser/extension folder.
See also this answer about Thunderbird (by me). The same steps worked for Firefox before application signing was enforced. In Firefox 43, the signature checks can be disabled via about:config. The about:config workaround will supposedly stop working in Firefox 44.

Resources