Planview Universal Connector
Overview
The Planview Universal Connector extends the capabilities of Planview Viz by creating a path to generate Flow Metrics for any tool in your software toolchain from ideate to operate. This enables you to eliminate data silos between common tools and in-house or industry-specific solutions, providing a comprehensive view of your software delivery process.
Connector Setup Details
This section describes the basic steps needed to prepare your Planview Universal Connector for use with Viz.
Note: The Universal Connector requires software development by the customer to create an adapter that conforms to the Planview Universal Connector API specification.
Connecting to the Planview Universal Connector Repository
API Token Authenticator
Required Fields:
-
Location/Connection URL
-
Example Format: https://server.com/api
-
-
API Token Authenticator
OpenID Connect Private Key Signed JWT Authentication
Required Fields
-
URL for OpenID Connect credentials
-
The token endpoint. You can get this from the authentication servers well known configuration endpoint.
-
-
OpenID Connect client ID
-
The client ID registered with the authentication server.
-
The client must have the client credentials grant type enabled.
-
The client must have registered the public certificate given in the “RSA certificate and private key (.p12)” field
-
-
OpenID Connect scope
-
Public Certificate
-
A PEM encoded public certificate of the private key being used to sign JWTs included in the requests client_assertion parameter
-
-
RSA Private Key
-
A PEM encoded PKCS8 private key used to sign JWTs included in the requests client_assertion parameter.
-
Optional Fields
-
Key ID
-
The “kid” header of the JWT sent in the access token request
-
-
Resource Parameter
-
The Open ID Connect resource parameter sent in the access token request.
-
Required for versions of Microsoft AD FS prior to 2019.
-
Supported Artifacts
Supported Work Items
|
Supported Work Item Type |
Applicable Repository Versions |
Unique URL? |
|---|---|---|
|
Artifact |
Any supported repository version: |
Yes |
Supported Containers
|
Containers that can be modeled as Flow Items |
Applicable Repository Versions |
Unique URL? |
|---|---|---|
|
N/A |
|
|
|
Containers used to define which artifacts are included in an Artifact Set |
|
|
|
N/A (entire tool serves as a container) |
|
|
Supported Field Types
Planview Viz supports configuring rule-based modeling (i.e., conditional modeling) using the field types shown below.
Note: If one field of a given type is supported, others that are also that type in theory should also work. However, sometimes there are instances in which this is not the case due to the repository. So, while we can claim support for fields at the type level, there is a chance that some specific fields of a given type will not function properly.
|
Field Type |
|---|
|
|
|
|
|
|
|
|
String