---
title: PingFederate 11.1.4 (February 2023)
description: Fixed PF-32790
component: pingfederate
version: 13.1
page_id: pingfederate:release_notes:pf_release_notes_1114
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/release_notes/pf_release_notes_1114.html
llms_txt: https://docs.pingidentity.com/pingfederate/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: July 22, 2024
section_ids:
  resolved-issues: Resolved issues
  oauth-client-management: OAuth client management
  potential-security-vulnerability: Potential security vulnerability
  informing-adapters-of-end-policy-result: Informing adapters of end policy result
  managing-certificates-within-metadata-export: Managing certificates within Metadata Export
  cluster-data-replication: Cluster data replication
---

# PingFederate 11.1.4 (February 2023)

## Resolved issues

### OAuth client management

Fixed PF-32790

When managing OAuth clients, we've resolved a defect where selecting the **Require JWT Secured Authorization Response Mode** text toggled the incorrect checkbox.

### Potential security vulnerability

Fixed PF-32805

We've resolved a potential security vulnerability that is described in security advisory [SECADV033](https://support.pingidentity.com/s/article/SECADV033-Cross-Site-Request-Forgery-on-PingFederate-Local-Identity-Profiles-Endpoint).

### Informing adapters of end policy result

Fixed PF-32890

When processing policy fragments, all adapters invoked in the fragment now correctly execute their respective post-processing step (if applicable) to inform the adapter of the end policy result.

### Managing certificates within Metadata Export

Fixed PF-32965

Managing certificates within the **Metadata Export** flow no longer displays or saves an empty list of certificates, clearing out existing ones in the process. For more information, see [Metadata export](../administrators_reference_guide/pf_metadata_export.html).

### Cluster data replication

Fixed PF-32983

We've resolved a defect where cluster data replication could remove keys from engine node's `pf.jwk` file instead of merging and retaining the keys.