Setting Browser-Authentication Options

Note: For replay, use browser authentication settings if you want all virtual users to login using the same credentials. If you want each virtual user to connect with different login credentials, specify the credentials using project attributes. See Project Attributes in the BDL Function Reference for detailed information or use script customization with data files.

In Silk Performer, expand the Profiles node in the Project tree.
Right-click the profile that you want to configure and choose Edit Profile.
Tip: Alternatively, you can choose Settings > Active Profile from the menu bar.

The Profile - [<profile name>] dialog box opens, and the Replay category is displayed in the shortcut list on the left.
In the shortcut list, click the Web (Protocol-level) icon.
Click the Authentication tab.
In the User authentication area enter a Username and Password for authentication when connecting to a protected, remote server.
The following applies only for recording:
1. In the shortcut list, click Record.
2. Enable Generate new user authentication token in recorder.
  Note: When recording a script, the Silk Performer Recorder forwards the authentication data that was generated by the browser to the server. This is the default behavior. However, you can also instruct the Recorder to generate a new user authentication token and send that to the server. For more information, see the note below.
In the Proxy authentication area, enter a Login name and a Password for proxy authentication login (required when connecting to the Internet through a proxy server).
Click OK to save your settings.

Note: By default, the Silk Performer Recorder acts as a blind proxy and forwards the authentication data that was generated by the browser to the server. If the browser is missing the correct authentication information, it can prompt the user for it, also during recording. This default behavior causes no additional overhead for the Recorder. However, the default behavior does not work if the server requires channel binding (also known as extended protection on IIS servers). In such a case, enable Generate new user authentication token in recorder. The Recorder will then replace the authentication data that was generated by the browser using the credentials specified below the check box. However, be aware of the following facts: (1) User name and password have to be configured before the recording is started. (2) This mode causes additional overhead for the Recorder. (3) When the browser prompts you for credentials, the credentials you enter are ignored, because the Recorder automatically replaces these with the credentials defined in the settings. Make sure to click OK (not Cancel) to close the prompt.