Releases: pingidentity/ping-cloud-base
Releases · pingidentity/ping-cloud-base
v1.6.1
v1.6.0
- Added multi-region support of PD, PF, and PA
- Added periodic CSD uploads for PF admin, PA admin/engine
- Leveraged topology-aware volume provisioning for all StatefulSets
- Added Web Application Firewall to PF/PA admin UIs, Kibana, Grafana and Prometheus
- Added SIEM for PingFederate
Complete changelog here
v1.5.0
- Added Pingaccess WAS (Web Access Security) layer to the deployment so admin consoles may be exposed to the Internet
- Enabled SIEM (Security Information and Event management) for PingDirectory
- Created a discovery service for discovering variables stored in AWS SSM parameter store across regions
- Switched to using SKBN instead of AWS CLI in deployment automation
Complete changelog here
v1.4.3
v1.4.2
- Fixed ingresses to force HTTP traffic to be redirected to HTTPS
- Fixed a data loss issue in PingFederate admin that was caused by switching it to use a persistent disk
- Fixed a typo in PingDirectory's BACKENDS_TO_BACKUP environment variable
- Fixed the base DN to point to the right backend in PingDirectory's purge-sessions script
Complete changelog here
v1.4.1
- Changed PingAccess 'podManagementPolicy' to 'OrderedReady' to support zero-downtime update of engines
- Fixed encryption errors encountered while restoring PingDirectory user and operational data from backups
- Disabled automatic key renewal on the Bitnami sealed-secrets controller
Complete changelog here
v1.4.0
- Updated Container Insights to silo each product log file into log streams
- Allow pre-launch configuration to be customized for PingFederate
- Added support for in-place upgrade of the PingFederate admin server
- Added support for PingAccess artifact service
- Changed the PingAccess file and database passwords from its default value
- Downsized PingDirectory persistent volume to reduce cost
- Updated PingDirectory deployment automation to remove its persistent volume on scale-down to reduce cost
Complete changelog here
v1.3.2
v1.3.1
- Fixed PingAccess engine flapping due to HPA and Flux interfering with each other
- Fixed PingAccess deployment automation to enable verbose logging only if VERBOSE is true
- Fixed PingDirectory backup to include PingFederate data under the o=appintegrations backend
- Fixed PingDirectory rolling update to preserve the server's MAX_HEAP_SIZE setting
- Fixed PingFederate restore job to not fail if there are too many backup files
Complete changelog here
v1.3.0
- Added support for PingAccess deployment automation, including initial deployment of a cluster, auto-scaling, auto-healing of failed admin and engine instances, encrypted backup of the master key for disaster recovery upon instance and AZ failure
- Added the ability to capture and upload PingFederate CSD archives to S3, if using AWS
- Updated PingDirectory from 8.0.0.0 to 8.0.0.1
- Updated PingFederate from 10.0.0 to 10.0.1
- Updated cluster-autoscaler from v1.13.9 to v1.14.4
- Added the ability to define service dependencies between Ping application using the WAIT_FOR_SERVICES environment variable
Complete changelog here