PingIdentity DevOps Docker Builds - Version 1908
August 2019,
Note:
- Use tags when wanting to ensure that underlying software will not change. The DevOps program delivers all latest features to
:edge
for container images, andmaster
for repositories. - Tags correlate to 3 repositories: Docker-Builds, Getting-Started, Server-Profiles. Be sure to use each of the repositories as appropriate for consistency (e.g. append
:1908
to images and use server-profiles that are part of the 1908 tag. Gitbook has versioned documentaion as well.)
Release Contents
-
New Product Image: PingDataGovernance
In light of PingDataGovernance's (PDG) significant 7.3.0 updates, there has been demand for a containerized version.
Details on the product here. This initial image contains the PDG runtime engine and not the Policy Administration UI. Externally created policies should be injected to the runtime via dsconfig in a server profile. -
PingDirectory 7.3 Enhancements
As PingDirectory replication matures in the containerized format, additional use cases have been considered and improved upon; namely, handling scenarios with individual pod crashes and returns into the topology. -
Support for PingAccess Configuration Import
A configuration file nameddata.json
can be sent in via server-profile. To achieve this, be sure to include pa.jwk and structure your server-profile like so:. ├── instance │ ├── conf │ │ └── pa.jwk │ └── data │ └── data.json.subst
-
Additional improvements
- Vulnerability improvements to PingDataConsole. Removed unnecessary Tomcat default content.
- Ping DevOps User/Key or valid license in server-profile now required for using all images. To get one see here:https://pingidentity-devops.gitbook.io/devops/prod-license
-
Latest Product Versions
The following product versions will be used when using thelatest
tag on PingIdentity Docker Images:
PingFederate - 9.3.1
PingDirectory - 7.3.0.1
PingAccess - 5.3.0
PingDataGoverenance - 7.3.0.0
PingDelegator 3..4.0