Central Governance 1.1.1 Release Notes

New features and enhancements

Registration approval

Registration approval allows a Central Governance user that has appropriate rights to approve or reject a pending Transfer CFT registration before certificates are generated and deployed on the Transfer CFT.

Impact management

Central Governance provides warnings if you modify a Transfer CFT configuration or a Partner communication profile configuration that is used in flows if there is an impact on one or more flows. In addition, if certificates that are used in flows expire, the flow is impacted automatically and warnings signal that the flow is incomplete due to the invalid certificate.

REST API

You can now use REST APIs (Application Programming Interfaces) to provide resources for configuring A2A flows and flow components.

Remove update packages

Provides an easy method for users to remove product update packages via the Central Governance interface.

Transfer CFT serialization

You can enables file transfer serialization in the flow definition for Transfer CFT.

Copy user-defined roles and privileges

Provides the ability to copy user-defined roles and privileges in order to simplify the creation process or for template usage.

Known issues

The following are known issues in this version.

SecureTransport

Flow limitations when using SecureTransport

The following are limitations and workarounds when using SecureTransport in flows.

Receiver pulls files from SecureTransport over PeSIT

If files are available to pull but the flow manager changes the Partner’s PeSIT login in the flow and re-deploys it, then the partner can no longer download the available files. This is because the files are in /<PeSIT identifier>/OLD_PESIT_LOGIN and remain there indefinitely unless removed manually. The same situation can occur if the PeSIT identifier is changed in the flow.

SecureTransport receives files over PeSIT and receiver pulls files from SecureTransport over PeSIT

If the same PeSIT identifier and SecureTransport PeSIT login is configured in the flow both before and after the SecureTransport relay the result is only one transfer profile representing the PeSIT flow (name= <PeSIT identifier>). This is because receive properties for file encoding and record format configured in the first part of the flow are overwritten at deployment by properties setting the receiver as pulling files from SecureTransport.

Replace an unmanaged product with a managed SecureTransport in SSL flows

Rather than have a flow with an unmanaged product sending files to Transfer CFT via SSL, replace the unmanaged product with a registered SecureTransport. When changing the flow, you must provide a private certificate for SecureTransport to authenticate to Transfer CFT. You cannot use the same certificate used for the unmanaged product being replaced. You must upload a certificate chain containing a new SSL certificate in the client communication profile.

SecureTransport upgrade does not report the new product version

After upgrading SecureTransport outside Central Governance, the old product version is displayed in the product list and product detail view. Moreover, the product version does not report the Service Pack for SecureTransport.

Visibility

Flows with file processing execution failure are reported as successful in Visibility

When a flow execution fails at a post-processing step on a relay or target, the flow is seen as successful in Visibility because from the source standpoint the flow is seen as “Completed”. The State order defines that “Completed” state is after “Post-processing” state.

When transfer is in INTERRUPTED state, no flow alert is sent

When the transfer fails on a Relay with INTERRUPTED state, for instance the target is not reachable, and if there are subscriptions to the active Flow error alert, the alert is not triggered due to the isAlert flag being incorrectly set to 0 instead of 1.

Identity and access management limitations

  • The user interface only supports ASCII characters. You cannot use non-ASCII characters.
  • You cannot rename an organization.
  • When you rename a role that has been assigned to users, the privileges associated with the role are suspended until a user accesses the User List page.
  • When using an identity store of type Active Directory, group hierarchy is not supported. This means when mapping an internal role to an external super-group, the user linked indirectly to the super-group does not inherit the rights. As a workaround, map the internal role to the sub-group directly linked to the user.
  • After accessing the separate user interfaces for Central Governance services — Access and Security, Visibility and Dashboards — there is no way to log out of those UIs, in the same way that you can log out of the Central Governance UI. You can exit the other UIs individually by closing their browser tabs, or closing the browser to end all UI sessions. Logging out of Central Governance also makes the other UIs inactive.

Related documentation

Central Governance has documentation covering all aspects of the product. This includes:

  • Central Governance Installation Guide
  • Central Governance User's Guide
  • Central Governance Security Guide
  • Capacity Planning Guide, which focuses on managing Transfer CFTs with Central Governance

Documentation is available on the Help Center tab in the Central Governance user interface.

Support services

The Axway Global Support team provides worldwide 24 x 7 support for customers with active support agreements.
Email support@axway.com or visit support.axway.com.

Related Links