I'm getting this error after running the script in jmeter tool.
Validation of viewstate MAC failed. If this application is hosted by a
Web Farm or cluster, ensure that configuration specifies
the same validationKey and validation algorithm. AutoGenerate cannot
be used in a cluster.
Dev team has enabled machineKey=true
Most probably you didn't correlate VIEWSTATE parameter, you need to extract it from each response and add as a parameter to the next request. Normally people use Regular Expression Extractor for this.
See ASP.NET Login Testing with JMeter article for details.
Related
I have created script using Blazemeter.
But it is getting error related to authenticate, Can you please guys help me how to authenticate Ms. Crm Login. Thanks in advance
It's not sufficient to just "record" the test as modern web applications heavily rely on dynamic parameters, for Microsoft technologies based web apps the most common are ViewState and EventValidation
When you're recording the test it just captures the "current" values while the server expects the values to be dynamic so you need to:
Extract the dynamic values from the previous responses using suitable JMeter Post-Processors
Save them into JMeter Variables
Replace recorded values with the variables from step 2
See ASP.NET Login Testing with JMeter for example implementation.
In addition in certain cases application might use external subsystems for authenticating the users, in that case you need to add properly configured HTTP Authorization Manager to your test plan
I have recently started using JMeter and I'm still trying to get to grips with it. I am trying to use JMeter to performance test Dynamics CRM. I have created a test plan and included a thread group with the HTTP authorization manager. I have added an HTTP Request and set the path to the 'homepage'. This appears to be working, but when I try some other requests I am getting the following response body :
'Important: Microsoft Dynamics CRM makes extensive use of your Web browser's client-side abilities. You either have one of these features turned off or your security settings are set so high that they prevent these features from being used. To enable these features, change your browser settings to allow the Microsoft Dynamics CRM site to run JavaScript. '
My question is how can I configure JMeter to avoid this error? As far as I understand, JMeter it does not make use of a browser unless you're recording a test script so I'm unsure how I can change settings.
It seems that Dynamics uses a lot of browser-side JavaScript. JMeter has a plugin which can execute this JavaScript.
However...you will need to be fairly sophisticated in what you measure. The performance of the JavaScript will depend on your test hardware, and won't represent what "normal" users see - you're testing the performance of JavaScript in a browser, rather than the Dynamics server.
An alternative would be to look at the calls the JavaScript makes to server-side resources, and capture those as JMeter calls. This does mean reverse-engineering the application logic to understand how the Dynamics client-side application interacts with the server.
Our organization has SSO authentication via an Apache reverse proxy, which is currently working flawlessly. I was surprised how easy it was to configure!
Now that I have this set up, however, I find that I am not able to submit jobs using sonar-runner. When I look at the logs, I see that every access is redirected to the Federated SSO login page.
Is there some additional configuration that needs to be done to allow scans to go through without being authenticated? Or perhaps some configuration options that need to be passed to the sonar-runner itself?
EDIT: We did consider a couple of options.
First, we thought about allowing only the URLs necessary to submit jobs to pass through the reverse proxy without authentication. This is a tedious process at best and allows a path of entry into the service itself without authentication.
Second, we thought about passing a user token along with the request. There are two issues with this approach. First, the existing URL is set up to authenticate using a three-legged approach. As far as I know, I can't set up both two-legged and three-legged authentication for the same URL. Second, we are submitting jobs using the Sonarqube plugin in Jenkins. Without modifying the plugin itself, there is no way to get a user token to pass through to the submit request.
Our workaround for the moment: Since both systems are running in Docker containers, we submit from Jenkins by passing it to the IP address of the Sonarqube container. This has the undesired effect of formatting the Sonarqube report links with a 172.17.0.x address rather than the FQDN.
How can I perform Load testing on Oracle Portal Application Using Jmeter?
I recorded the activity using jmeter proxy and run the recorded request but I got unrealistic results.
Oracle portal is nothing but an ADF application, so it can be testes as any other ADF application.
You basically need an approach as Pino uses here:
http://soadev.blogspot.co.uk/2014/04/jmeter-load-test-oracle-adf-applications.html
Registering tests with JMeter is a tricky business, you need to validate your scenario once recorded by running it with only one thread and check the server logs (in case you use your custom logger) to make sure the functionality on the server is being executed.
I am trying to make a performance testing by using the JMeter for the User registration process in Chat application,which is developed by using openfire and XMPP. I am providing the different user details through CSV Data set.The issue i am facing is, The newly provided user details are not getting to save in the XMPP. As per discussion with the developers, They are using SMACK plugin(.jar files inside the programs) for the registration and other process.(i.e) The Jmeter is recording only for the API calls,Not recording the smack plugin activities due to this i am struggling to make the performance testing for the new user registration process in the chat application.
Thanks in advance.
JMeter Test Script Recorder can only record HTTP traffic through proxy so if you configured proxy for smack plugin then recording cannot happen due to protocol not being understood.
Otherwise it's proxy misconfiguration.