How to Integrate CA Clarity PPM with VersionOne › Configure CA Clarity PPM for VersionOne

Configure CA Clarity PPM for VersionOne

Configure CA Clarity PPM for VersionOne so data can synchronize between them. To complete this procedure, use the following values that you generated and saved in the previous procedure to authorize CA Clarity PPM for VersionOne:

• OAuth tokens generated in JSON form
• Tokens from the downloaded JSON file.

Note: After installing the connector and before starting the background services, edit the default URL that the product uses to access VersionOne. The default URL is not a valid web address. To point to your correct VersionOne instance, update this URL.

Follow these steps:

1. Log in to CA Clarity PPM.
2. Open Administration, and from General Settings, click Remote API Setup.

   If multiple plugins are installed, the Remote Access Implementations page appears. Select VersionOne and click the link for it to go to the remote API admin settings page for the plugin. If multiple plugins are not installed, you go directly to the Remote API Admin Settings page.

3. Complete the following information:

   Remote Environment Endpoint URL

   Specifies the URL that the product uses to access the VersionOne production or sandbox environment. For example: https://www6.v1host.com/ClarityTest/

   Remote System Base URL

   Specifies the URL that the product uses to access the remote system. You can either enter the same URL as the remote environment endpoint or leave this field blank.

   Client Name

   Defines the name that the authorization server assigned to the client application at registration. Enter this value from the downloaded JSON file.

   Client ID

   Defines the unique ID that the authorization server assigned to the client application at registration. Enter this value from the downloaded JSON file.

   Client Secret

   Defines the unique password that the authorization server assigned to the client application at registration. Enter this value from the downloaded JSON file.

   Auth URI

   Defines the authorization URL that you used to authorize the product for VersionOne using the token generator. For example, https://www6.v1host.com/ClarityTest/oauth.v1/auth.

   Token URI

   Defines the access token URL that you used to authorize the product for VersionOne using the token generator. For example, https://www6.v1host.com/ClarityTest/oauth.v1/token.

   Scope

   Defines the endpoints that the integration is authorized to use. For example: apiv1 query-api-1.0 ~/notification.v1.

   Redirect URI

   Defines the redirect URI that the resource owner uses to redirect back to the client application after successful authorization. This value is not needed since you used a token generator (for example, Runscope).

   Access Token

   Defines the access token that you generated in JSON form using the OAuth token generator tool. Use the value that you saved in Notepad when authorizing the product for VersionOne.

   Refresh Token

   Defines the refresh token that you generated in JSON form using the OAuth token generator. Use the value that you saved in Notepad when authorizing the product for VersionOne.

   Auth Token

   Defines the authorization token that is generated when the request is submitted to the server. You can also leave this field blank.

4. (Optional). Complete the proxy server information and save your changes.

   The product is now integrated with VersionOne.