Skip to main content
Planview Customer Success Center

Micro Focus ALM/Quality Center

Micro Focus Logo




Micro Focus Application Lifecycle Management (ALM) and Quality Center (QC) (formerly HPE ALM/QC) provide users with support for requirements, test, and defect management.

Testers and Testing Centers of Excellence rely on Micro Focus ALM/Quality Center to provide the infrastructure they need to execute their work.



Connector Setup Details

This section describes the basic steps needed to prepare your Micro Focus ALM/Quality Center instance for use with Viz. 

Minimal User Permissions & Viz User

We recommend that you create a new user within your external tool, to be used only in Viz. This is the user information you will enter when setting up your tool connection within Planview Viz. By creating a new user, you will ensure that the correct permissions are granted. 

In general, your user account should have sufficient permissions to read artifacts in your tool. 

Your user should have a secure password or token. Please be aware that Viz will not allow you to save a tool connection utilizing a weak password/token, such as 'tasktop.'

Connecting to the Micro Focus ALM/Quality Center Repository

Standard Authentication

Required Fields:

Micro Focus ALM Tool Connection Screen - Standard Authentication


Standard Authentication with OAuth2.0 Proxy Authentication

ALM: 17.0.1 On Premise

The MF ALM connector supports Standard Authentication with OAuth2.0 Proxy Authentication flow to authenticate with the proxy through an identity provider. It utilizes a base64-encoded representation of the username and password for authentication.


Required Fields:

  • Location/Proxy URL
  • Identity Provider URL: Used to obtain the authentication token from the identity provider
  • Client ID: A unique identifier assigned to a client application when it is registered with the identity provider
  • Client Secret: Used to authenticate the identity of the client application when making requests to the identity provider
  • Scope: Specify the access permissions
  • Route: Based on the route, the request is redirected to the corresponding endpoint configured in the proxy
  • Username: The username associated with the account used for authentication
  • Password: The password associated with the provided username for authentication


  1. HTTP Request Headers:
    • Authorization: OAuth2 token obtained from the Identity Provider
    • RepoAuthorization: base64-encoded representation of the username and password
    • AuthMode: Set to "pat" (Personal Access Token)
    • Route: Specify the route to the specific repository
  2. Proxy Authentication with Identity Provider:
    • The proxy authenticates the OAuth2 token provided in the Authorization header with the Identity Provider, verifying its validity and checking for necessary permissions
  3. Validation and Redirection:
    • Upon successful validation, the proxy replaces the content of the Authorization header with the RepoAuthorization token
    • The route header specifies the destination repository for redirection
    • If the validation process encounters an error, an error response is sent back to the client

API Key Access

Required Fields:

  • URL  
  • Client ID 
    • see Micro Focus ALM/Quality Center instructions here
  • API Key Secret
    • see Micro Focus ALM/Quality Center instructions here

Micro Focus ALM Tool Connection Screen - API Key Access



Supported Artifacts

Supported Work Items

Supported Work Item Type

Applicable Repository Versions

Unique URL?


Any supported repository version:


Supported Containers

Containers that can be modeled as Flow Items

Applicable Repository Versions

Unique URL?




Containers used to define which artifacts are included in an Artifact Set




Any supported repository version:




Supported Field Types

Planview 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.

Standard Field Type

How is field type referenced in the repository?

Sample Repository Fields Supported

Particular Repository Fields NOT Supported

1checkicon.png String




Formatted ID


1checkicon.png Single Select

Lookup list



Direct Cover Status



1checkicon.png Multi Select

Lookup list (multiple values)

Target Release

Target Cycle


1Not_allowed.svg.png Boolean