...
- Each setting should be entered on a single line.
- We highly recommend that you use encoded passwords to ensure successful authentication and increase the level of security; see Creating an Encoded Password.
- If you are importing preferences from settings specified on DTP and you want to override these settings from the GUI, you can clear the Use DTP settings option on the appropriate page, then manually configure the settings.
- If any settings problems are detected during a test run, details will be reported in the command line output.
- If you are running cli mode from a developer/tester desktop (as opposed to from a Server machine), use the
tasks.clear=false
option to ensure that your results from previous runs are preserved.
...
Setting | Purpose |
---|---|
dtp.enabled=true|false | Determines whether the current C/C++test installation is connected to DTP. |
dtp.url=[url] | Specifies the URL to the DTP server. The default port numbers for DTP are:
If DTP is deployed to a location other than the root of the host server, the URL should include a context path (a relative path from the host name). This may be the case if your organization uses a reverse proxy. Refer to the DTP documentation for additional information about reverse proxy server configuration and context path configuration. Example: Example including a context path: |
dtp.user=[username] | Specifies the username for DTP server authentication. |
dtp.password=[password] | Specifies the password for DTP server authentication. We highly recommend that you use an encoded password to ensure successful authentication and increase the level of security; see Creating an Encoded Password. |
report.dtp.publish =true|false | Enables or disables reporting results to DTP server. |
dtp.project=[project_name] | Specifies the name of the DTP project that you want these results linked to. |
dtp.additional.settings=[KEY1\=VALUE1\nKEY2\=VALUE2...] | Specifies advanced settings for reporting results to DTP. |
dtp.autoconfig=true|false | Enables autoconfiguration with C/C++test settings stored on the DTP server |
...
Setting | Purpose |
---|---|
parasoft.eula.accepted=true|false | Allows you to accept the terms of Parasoft End User License Agreement (EULA). Default: false |
cpptest.license.use_network=true|false | Enables or disables retrieving a network license. Example: Default: true By default, C/C++test will try to retrieve a license form License Server on the DTP configured as your primary DTP server; see Parasoft DTP Settings. If you want to configure another License Server, enable the |
cpptest.license.local.password=[password] | Specifies the local password that you want C/C++test to use. |
cpptest.license. local.expiration=[expiration] | Specifies the expiration date of the local license. Default: 0 |
cpptest.license. network.edition=[edition_name] | Specifies the type of the network license that will be retrieved from DTP or Licence Server. This setting requires that the Acceptable edition names:
Default: Example: The following configuration enables the license optimized for desktop usage. |
cpptest.license.custom_edition_features=[feature name] | Specifies the features you want to enable in the custom edition of the C/C++test license. You can use a comma-separated list to specify more than one feature. Acceptable feature names:
|
cpptest.license.wait.for.tokens.time=[time in minutes] | Specifies the time that C/C++test will wait for a license if a license is not currently available. For example to make C++test wait 3 minutes for license tokens, use Default: 0 |
cpptest.license.autoconf.timeout=[seconds] | Specifies the maximum number of seconds C/C++test will wait for the license to be automatically configured from License Server. Default: 20 |
license.network.use.specified.server =true|false | Enables or disables retrieving the license from a custom License Server specified with the Example: Default: false |
license.network.url=[url] | Specifies the the URL to the standalone License Server or secondary DTP that you use to obtain the license. It requires the The default port numbers are:
If DTP is deployed to a location other than the root of the host server, the URL should include a context path (a relative path from the host name). This may be the case if your organization uses a reverse proxy. The context path is not supported for a standalone License Server. Refer to the DTP documentation for additional information about reverse proxy server configuration and context path configuration. Example: license.network.url=http://jade.mycompany.com:8080 Example including a context path: license.network.url=https://aurelia.mycompany.com:8443/contextPath |
license.network.auth.enabled= | Enables or disables authentication on the secondary DTP server specified with the It requires the |
license.network.user=[username] | Specifies the username for authentication on the secondary DTP server specified with the Example: |
license.network.password=[password] | Specifies the password for authentication on the secondary DTP server specified with the Example: |
...
Setting | Purpose |
---|---|
oidc.enabled= | Enables or disables user authentication via OpenID Connect. The default is |
oidc.issuer.uri=[uri] | Specifies the URI of the OpenID Connect server where your DTP is registered. |
oidc.client.id=[id] | Specifies the ID registered on your OpenID Connect server. |
oidc.client.secret=[password] | Specifies the password provided by your OpenID Connect server. |
oidc.cli.mode=devicecode|certificate | Specifies the method that will be used to authenticate the user on the OpenID Connect server. If set to If set to Default: |
oidc.devicecode.token.file | Specifies the path to the custom token file containing user authentication information. For example:
|
oidc.keystore=[path] | Specifies the path to the keystore file that stores the certificate to authenticate the user on the OpenID Connect server. |
oidc.keystore.password=[password] | Specifies the password to the the keystore file that stores the self-signed client certificate. We highly recommend that you use an encoded password to ensure successful authentication and increase the level of security; see Creating an Encoded Password. |
oidc.keystore.alias=[alias] | Specifies the alias you want to use to authenticate on the OpenID Connect server. You may need to configure this setting if your keystore file contains multiple entries. Example: |
oidc.callback.host=localhost | 127.0.0.1 | This setting specifies the local callback host configured in the IDE to communicate with the OpenID Connect server. This is an IDE-related setting and is not intended for command line use. The default is |
oidc.callback.port=0 | [port number] | This setting specifies the callback port number configured in the IDE to communicate with the OpenID Connect server. This is an IDE-related setting and is not intended for command line use.
The default is |
oidc.callback.timeout=[seconds] | This setting specifies the maximum time allowed for providing user credentials on the authentication page to authenticate on DTP via OpenID Connect when working with C/C++test in the IDE. This is an IDE-related setting and is not intended for command line use. The default is |
...