NeoLoad supports the following authentication mechanisms:
For more information, click the image below to see the Neotys video about authentication:
SPNEGO is at the heart of the HTTP Negotiate authentication mechanism. When using SPNEGO, the browser and server negotiate as to which underlying mechanism to use, Kerberos or NTLM. If Kerberos -the default protocol- fails, Negotiate will try NTLM.
Note that Integrated Windows Authentication on Microsoft IIS uses both Kerberos v5 and NTLM authentication.
For performance reasons however, NeoLoad uses NTLM in place of SPNEGO as the default underlying mechanism for Negotiate, since SPNEGO+Kerberos has a major impact on Load Generator performance. When SPNEGO+Kerberos is used, a Load Generator cannot generate as many Virtual Users.
Enabling SPNEGO therefore, is not recommended. However, if it is absolutely required, please follow this procedure:
/conf/controller.propertiesfile in a text editor.
[Authentication]scheme.negotiate.subprotocol=key, change the value to
spnego(default value is
/conf/krb5.conffile in a text editor.
forwardable = true.
Some servers support multiple schemes for authenticating users. NeoLoad prioritizes them in the order
Basic to reflect the order used by regular browsers.
In certain cases, you may wish to change this default order: