0
votes

I am trying to record an internal website for which i need to enter credentials that is not same as the windows credential. Later on the same test needs to be run for more than one user. i know how to use the csv file to pass the parameters - username and password.

For Windows Authentication i have added Authorization manager.

From Fiddler i checked it was NTLM authentication(though i am not sure yet) and i did enter the values for NTLM authentication in Authorization Manager.

Now when i try and record the internal website - i cannot even go to homepage after the windows credentials, it keeps on spinning.

When i check the Authorization Manager, i find an extra line added for kerberos Authentication as shown in Picture: enter image description here

My query here is: 1)why is it recording it as kerberos 2)where is it saving the username and password 3)why is it not loading the website- always keeps spinning and i have to stop it 4)I have tried Kerberos settings and then record, but its not working either , could it be i am using the wrong values in the kerb5.conf file , how do i debug.

Kind of stuck at the moment.

Thanks for help!

1

1 Answers

0
votes

If you're uncertain what authentication is being used under the hood - just ask around, application developers or network administrators should be aware of the external authentication scheme. You can also try using a 3rd-party tool like Kerberos Authentication Tester

I don't think you can record and replay Windows authentication so it makes sense to start recording some time after the login screen as long as you can login using JMeter

  1. Looking into JMeter source

    // if HEADER_AUTHORIZATION contains "Basic"
    // then set Mechanism.BASIC_DIGEST, otherwise Mechanism.KERBEROS
    
  2. In case of Kerberos credentials are saved directly in the HTTP Authorization Manager in form of ${AUTH_LOGIN} and ${AUTH_PASSWORD}, real credentials are not stored anywhere
  3. Most probably your application doesn't receive valid authentication context therefore it cannot proceed
  4. Add sun.security.krb5.debug=true line to system.properties file (lives in "bin" folder of your JMeter installation), JMeter restart will be required to pick the property up.

    More information: