Due to the specifics of implementation of Kerberos authentication, in the Route and Record Non-Virtualized Requests routing mode, authentication requests are normally not recorded correctly for servers that use Kerberos authentication. They can be recorded only if the virtual service and the tested server are running on the same computer, and both of them can be addressed through localhost. However, this is an exception, because quite often, virtual services and servers function on different machines.
To work around the issue, you can try using API Discovery:
-
Open the API Discovery window. You can do this by selecting the APIs (Virtual) node in the Navigator and clicking Discover on the toolbar:
Click the image to enlarge it.
-
Switch the discovery engine to the Proxy mode:
Click the image to enlarge it.
The window will display information on the proxy parameters:
Click the image to enlarge it.
See Using ReadyAPI as Proxy for details.
-
Configure your client application using the information you see in the Discovery window.
-
Send authentication requests from your client application to the server. ReadyAPI will work as a proxy between the client app and the server. It will trace the requests and responses and display them on the Transactions page:
Click the image to enlarge it.
Note: Depending on the client configuration, the authentication steps can be recorded as several requests. -
Stop recording and then click Add to Existing Virtual Service to add the recorded requests and responses to your virtual service:
Click the image to enlarge it.
Now, the authentication requests and responses will be in your virtual service.