Introduction

Connecting to DTP allows you to obtain the network license and extend team-working capabilities, such as:

• Reporting analysis to a centralized database (see Sending Results and Publishing Source Code to DTP)
• Sharing test configurations
• Sharing static analysis rules

In addition, DTP aggregates and prioritizes data collected from analysis tools, as well as performs additional analysis to help you optimize development processes; see About the Parasoft Development Testing Workflow for details.

Configuring Connection to DTP Server

The connection must be configured in the .properties configuration file (see Configuration Overview). Set the following properties to configure the connection:

• dtp.url=[URL] 
• dtp.user=[USER]
• dtp.password=[PASSWORD]

Anchor
Encoded Password Encoded Password

Creating an Encoded Password

Jtest can encrypt your password, which adds a layer of security to your interactions with DTP Server. Run the following command to print an encoded password:  

-encodepass [MYPASSWORD]

Copy the encoded password that is returned and paste it into the jtest.properties file:

dtp.password=[ENCODED PASSWORD]

Anchor
openID_connect_config openID_connect_config

Configuring OpenID Connect in the .properties File

DTP ships with support for OpenID Connect user authentication (see the DTP User Guide for details). If OpenID Connect is enabled for your DTP server, you must configure Jtest to authenticate users via OpenID Connect.

Configure the following settings in the .properties file where the connection to your DTP server is configured.

If device code authentication will be used (default):

• oidc.enabled=true
• oidc.cli.mode=devicecode[method that will be used to authenticate the user on the OpenID Connect server. See Using Device Code Authentication]
• oidc.issuer.uri=[URI of the OpenID Connect server]
• oidc.client.id=[ID provided by the OpenID Connect server]
• oidc.devicecode.token.file=[path to the custom token file containing user authentication information]

If certificate authentication will be used:

• oidc.enabled=true
• oidc.cli.mode=certificate[method that will be used to authenticate the user on the OpenID Connect server]
• oidc.issuer.uri=[URI of the OpenID Connect server]
• oidc.client.id=[ID provided by the OpenID Connect server]
• oidc.client.secret=[password provided by OpenID Connect server]
• oidc.keystore=[path to the keystore file that stores the certificate to authenticate the user on the OpenID Connect server]

• oidc.keystore.password=[password to the keystore file; we highly recommend that you use an encoded password; see Creating an Encoded Password.]

See OpenID Connect Settings for details.

Anchor
device_code device_code

Using Device Code Authentication

If "devicecode" mode is enabled, the verification URI and user code are printed on the Jtest console. The user must use this URI and code to authenticate. If the authentication is successful, the information is saved to a token file (the path to the file is stored in the oidc.devicecode.token.file setting) and reused each time Jtest is run. If the information saved in the file becomes invalid, the user will need to authenticate again.

Anchor
about_DTP_workflow about_DTP_workflow

About the Parasoft Development Testing Workflow