Newly supported releases PingDirectory 9.0 (release notes).
Use PingCentral to configure PingFederate and PingAccess environments
PingCentral is now deployed with PingFederate and PingAccess environments. All of your development environments (development, testing, staging, and production) will be configured for you and accessible from PingCentral.
Use PingFederate Admin API to create password credential validator and LDAP client manager
You can now use the PingFederate Admin API to create the PingDirectory password credential validator and the LDAP client manager instead of using static XML. If the credential validator or client manager already exists, they will not be overwritten.
Hot and warm Elasticsearch index tiers added
Elasticsearch index lifecycle management (ILM) policies have been created, and a hot-warm-cold architecture has been implemented to improve performance and resiliency.
The indexer handles indexed data in a way that ages the data through several states. When the data is first indexed, it’s added to a hot data tier and remains there for 90 days. Data nodes that are not actively written to are moved to a warm data tier, where they remain for 180 days. Data not accessed for more than 180 days is not indexed.
Health check services added
Health check services, which provide operational status and performance data, were recently added to monitor internal APIs and clusters.
Configurable log-streaming pipeline added
You can now use a variety of different security analytics services and customize the ways log data is streamed. You can filter streamed data by application, log, and key words, and modify JSON files. Available security analytics services include:
- Customer S3 bucket
- Customer Cloudwatch ingestion
- IBM Qradar
- Azure Sentinel