...

If your machine is configured to use your own proxy, you should configure SOAtest and/or Virtualize to point to that proxy. This enables SOAtest and/or Virtualize to configure its internal proxy to forward all traffic to the specified proxy configured in Additional Preference Proxy Settings.

Console Settings

...

• Default timeout (milliseconds): Allows you to enter the length of delay (in milliseconds) after which SOAtest should consider your FTP, telnet, or HTTP requests to be “timed out.” The default is 30000 milliseconds.
• Report each duplicate error that occurs on the same line: Tells SOAtest to show only the first instance of duplicate errors that occur for the same line of code.
• Reset Cookies: Allows you to clear the current global cookies so that next HTTP invocations start a new session.
• Enable the Automatically backup project files option and specify a file size threshold for .tst and/or .pva files in the Warn on file size large than (MB) field to be notified when the size of the file exceeds the threshold. You can then reduce the size (and prevent performance problems) by dividing it into smaller filesby dividing it into smaller files.

Anchor
OpenAI OpenAI

OpenAI

The OpenAI panel allows you to configure the application to use your OpenAI or Azure OpenAI account to assist you when creating test scenarios. The model of OpenAI that is used must support function calling. Functionality has been tested on GPT-3.5 turbo and GPT-4. Note this functionality is only supported with a license that has "LLM Integration" enabled.

Using OpenAI to create test scenarios requires access to your OpenAI or Azure OpenAI account. To enable it, set the following preferences:

• Enable: When enabled, OpenAI is available when creating test scenarios from an OpenAPI/Swagger definition.

• Provider: Your OpenAI provider. Choose between OpenAI and Azure OpenAI.
• Configuration (OpenAI)
  • API key: Your OpenAI token.
  • Organization ID: The Organization ID you want to use when accessing the OpenAI client. Optional. If no Organization ID is supplied, the default organization ID for your account will be used.
  • Test Connection: Click to test the connection to OpenAI.
  • Model > Name: The name of the OpenAI model you are using, for example gpt-3.5-turbo-16k or gpt-4.
• Configuration (Azure OpenAI)
  • Resource Name: The Azure resource that contains your deployed Azure OpenAI model.
  • Deployment ID: The deployment name of your Azure OpenAI model.
  • API key: Your Azure OpenAI token.
  • Test Connection: Click to test the connection to Azure OpenAI.

Note: OpenAI may produce inaccurate information, which may affect product features dependent on OpenAI.

Anchor
OIDC OIDC

OpenID Connect

The OpenID Connect panels panel allows you to configure the application to authenticate users via your OpenID Connect server .

...

by setting the following:

...

• Enable: When enabled, OpenID Connect is available for authentication.
• Server
  • • Issuer URI: The URI of your OpenID Connect server.
    • Client ID: The ID registered on your OpenID Connect server.
    • Client Secret: The application's password to the OpenID Connect server.
    • Scopes: A space-separated list of scopes used during authentication to authorize access to a user's details.
    • Callback host: The local callback host required to communicate with the OpenID Connect server. The following options are available:
      • localhost: The localhost address will be used for communication.
      • 127.0.0.1: The loopback IP address 127.0.0.1 will be used for communication.
    • Callback port: The callback port number for communication with the OpenID Connect server. The following options are available:
      • Automatically select an open port: Automatically selects an open port (recommended).
      • Use port: Allows you to manually specify the port number.
    • Callback timeout: Specifies, in seconds, the maximum time the browser will wait for user credentials.

  ...

  • • Test Authentication

  ...

  • • : Click to open the OpenID Connect authentication page in your browser.

  ...

  • • You may be asked to provide your credentials in the browser window that opens

  ...

  • • .

  ...

  • Status: Shows the current OpenID Connect authentication status.

  Info
  Azure Active Directory users: Enter the redirect URL configured above under "Mobile and desktop applications" in Azure AD. For example, if Callback host is set to "localhost" and Callback port is set to "Automatically select an open port" (the default values), you would enter "http://localhost/oauth2_callback" for the callback URL in Azure AD.

  ...

  The Scripting panel allows you to specify properties used for custom scripts.

  • Java: For Java, you can specify the Java home directory and the path to the javac compiler. You need to specify these parameters if you want to compile Java methods in the editor.   

    Note
    title Note
    The javac compiler is not included.

    • Java home: Specifies the Java installation directory.
    • Javac classpath: Specifies the Java classpath.
  • JavaScript: If you create scripts using JavaScript, you can specify a script template in the Script Template field.
    • Script Template: Whatever code is specified in this field will be used as the default code for inlined scripting in the language with which the field is associated. This is primarily useful for setting default inputs and common global variables. Script templates apply to scripts used in Extension tools; they do not apply to JavaScript that runs in a browser context.

  • Jython: If you are using Jython scripts, you can specify the Jython Path variable. Jython scripting support can be used without setting this variable by specifying a script template in the Script Template field.

    • Jython Path: Specifies a list of directories to search for python modules that are not already included with Jython. Separate multiple directory paths using the OS default path separator (";" for Windows and ":" for Linux and macOS). If you set the Jython path then you need to restart SOAtest or Virtualize for the change to take effect.
    • Script Template: Code specified in this field sets a default template for Jython scripts used in the tool.

  • Timeout Settings: Specify how many minutes SOAtest or Virtualize should wait before attempting to stop an unresponsive script and log an error message.

  Security Settings

  
  You can configure default security settings for clients and Responders used in your projects. In most cases, the security settings can be overridden by configurations set locally in your suites:

  ...

  Info
  title Important
  In order to perform operations that use the XML Signature Verifier, XML Signer, or XML Encryption tools, or if using Key Stores, you will need to download and install the Unlimited Strength Java Cryptography Extension. For details, see Additional Preference Settings JCE Prerequisite.

  Keystores are specified at the test or responder suite level. If this option is selected, the following options are available in the Certificate and Private Key tabs:

  ...

  Setting	Purpose
  virtualize.license.use_network=true|false	Determines whether the current installation retrieves its license from License Server.
  virtualize.license.network.host=[host]	Specifies the machine name or IP address of the machine running License Server Configuration Manager. If your server uses the HTTPS protocol, prepend https:// to the hostname. This setting is deprecated.
  virtualize.license.network.port=[port]	Specifies the License Server port number. This setting is deprecated.
  virtualize.license.network.user=[username]	Specifies the username for authentication on the secondary DTP server specified with the license.network.url option. This option requires the license.network.use.specified.server and license.network.auth.enabled options to be set to true. Example: license.network.user=JohnDoe
  virtualize.license.network.password=[password]	Specifies the password for authentication on the secondary DTP server specified with the license.network.url option. This option requires the license.network.use.specified.server and license.network.auth.enabled options to be set to true and the the license.network.user to be configured. We strongly recommend encoding your password to ensure successful authentication and a secure connection. You can encode your password by running virtualizecli with the -encodepass flag.  Example: virtualizecli -encodepass mypassword  The command line tool will generate an encoded string that you can use in the configuration file.
  license.network.url=[url]	Specifies the License Server URL. Include the protocol and host name or IP address and, if appropriate, the port number and context path. Example: https://10.9.1.63:8443
  license.network.context.path=[path]	Specifies the path to the DTP License Server. The context path is a relative path from the host name specified with the license.network.host setting. This setting should only be configured if DTP is deployed to a location other than the root of the host server, which may be the case if your organization uses a reverse proxy. Configuring the context path is not supported for standalone License Server. Refer to the DTP documentation for additional information about reverse proxy server configuration and context path configuration.  This setting is deprecated.
  license.network.auth.enabled=true|false	Enables or disables authentication on the secondary DTP server specified with the license.network.url option. This option requires the license.network.use.specified.server option to be set to true.
  license.network.use.specified.server=[true|false]	This option enables Virtualize to connect to either DTP and License Server, or two instances of DTP simultaneously. Set to false if you want to retrieve a license from the DTP server specified with Additional Preference Parasoft DTP Settings.  If set to true, Virtualize will retrieve a license from the server specified with the license.network.url option.
  virtualize.license.network.edition=[edition_name]	Specifies the type of license that you want this installation to retrieve from LicenseServer. [edition_name] can be server_edition. To use a custom edition, do not set anything after the "="; simply leaving the value empty. Example: virtualize.license.network.edition=desktop_edition virtualize.license.network.edition=server_edition
  virtualize.license.autoconf.timeout=[seconds]	Specifies the maximum number of seconds this installation will wait for the license to be automatically configured from LicenseServer. Default is 10.
  virtualize.license. local.expiration=[expiration]	Specifies the local license that you want this installation to use.
  virtualize.license.local.password=[password]	Specifies the local password that you want this installation to use.
  virtualize.license.wait.for.tokens.time=[time in minutes]	Specifies the time that this installation will wait for a license if a license is not currently available.  For example, use virtualize.license.wait.for.tokens.time=3 to configure Virtualize to wait three minutes for a license token to become available.

  ...

  Note that with local licenses, the enabled features are specified via the generated password.

  ...