Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

When testing using Kerberos authentication why does authentication occur on every request instead of just once.

When testing using Kerberos authentication why does authentication occur on every request instead of just once.

NOTE: this is a critical patch which should be applied if you are testing Kerberos.

This is a known issue in Silk Performer 7.2 which can be fixed by applying Patch 11 (SP72_Patch_11_Kerberos). This patch fixes Kerberos authentication, where too many domain controller round trips have been done. Now only one roundtrip per domain/user combination is performed.

A call to the WebSetUserAuthNtlm function, to set the user name and password, clears the internal credential memory, so that subsequent Kerberos authentications of the same user force a new round trip to the domain controller (this enables the simulation of a system start). Consequently, if you want to avoid the domain controller round trips, place the WebSetUserAuthNtlm function call into the Init transaction.

To request this patch please contact Support and quote this resolution ID.

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:42
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.