Important considerations for upgrading to this version of PingDataGovernance Server:
If you are upgrading from PingDataGovernance 220.127.116.11 to 18.104.22.168 or 22.214.171.124, an updated version of the Policy Administration GUI is required.
The Allow Attributes and Prohibit Attributes advices have been deprecated. If a deployment requires the behavior that these advices provided, use a Server SDK to implement the appropriate behavior.
API Endpoints, which were introduced in 126.96.36.199, have been renamed to Gateway API endpoints.Warning: When performing an update, existing API Endpoint configuration objects are migrated automatically. To reflect this change, manually update your dsconfig scripts and other automated deployments or configurations.
If you are updating a multi-server topology from PingDataGovernance 7.0.x to 188.8.131.52, you must use the
--skipMirroredSubtreeUpdateTaskoption for the updater or the update fails. Alternatively, you can uninstall all but one of the servers to retain the base configuration, update the standalone server, install fresh servers on the new version, and add them back to the topology with the peer options. However, using the
--skipMirroredSubtreeUpdateTaskoption is the recommended path.
As a gateway, PingDataGovernance Server functions as a reverse proxy while in deployment mode. With 184.108.40.206, the Sideband API introduces an alternate deployment mode in which PingDataGovernance Server uses a plugin to connect to an existing API Lifecycle Gateway. In sideband deployment, the API Lifecycle Gateway handles requests between API clients and backend API services. The integration plugin intercepts all request data and passes it through PingDataGovernance Server, which authorizes requests and responses, and modifies request and response data.
The following table identifies issues that have been resolved with this release of PingDataGovernance Server.
Added a property to Advice types that limits their application to
The provided PingDataGovernance policies and deployment packages now apply access token validation policies only to the following requests:
The API Endpoint configuration type has been renamed to Gateway API Endpoint.
Update any existing dsconfig scripts that reference an API Endpoint. For example, a dsconfig command of create-api-endpoint must be changed to create-gateway-api-endpoint.
HTTP External Servers feature a new attribute,
When PingDataGovernance Server receives a
The Open Banking account request endpoint no longer requires a value for