User authentication

LoadRunner Developer supports the following types of user authentication:

When a web server requests authentication, the appropriate load.setUserCredentials step should be specified in the script.

For Basic and Digest authentication, username, password, and hostname are required:

load.setUserCredentials({
	username: "<username>",
	password: "<password>",
	host: "<host>:<port> "
});

For NTLM authentication, domain is also required:

load.setUserCredentials({
	username: "<username>",
	password: "<password>",
	domain: "<domain>",
	host: "<host>:<port> "
});

Note: You can hide password values in the script using load.unmask or load.decrypt APIs. For more information, see Encode sensitive data.

Kerberos authentication

LoadRunner Developer supports the Kerberos authentication protocol when replaying your scripts.

To enable Kerberos authentication:

  1. Create a krb5.ini Kerberos configuration file, and put it in an available folder. The krb5.ini file should contain detailed information about each domain (KDS and AS addresses) and trust chains.
  2. Save the full path name of the krb5.ini into the KRB5_CONFIG environment variable.
  3. Specify the appropriate load.setUserCredentials API parameters in the script.

    When the web server requests Kerberos authentication type, LoadRunner Developer uses the Kerberos configuration file to obtain tickets and complete the flow.

Back to top

See also: