---
title: PingFederate 12.3.5 (February 2026)
description: Info PF-38526
component: pingfederate
version: 13.1
page_id: pingfederate:release_notes:pf_release_notes_1235
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/release_notes/pf_release_notes_1235.html
llms_txt: https://docs.pingidentity.com/pingfederate/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
section_ids:
  new-features-and-enhancements: New features and enhancements
  par-parameters: PAR parameters
  resolved-issues: Resolved issues
  user-enumeration-in-policy-password-reset: User Enumeration in Policy Password Reset
  serialized-ognl-java-objects: Serialized OGNL Java objects
  kerberos-realm-validation-error: Kerberos realm validation error
  authentication-policy-error: Authentication policy error
---

# PingFederate 12.3.5 (February 2026)

## New features and enhancements

### PAR parameters

Info PF-38526

We've added a new configuration option to limit the Pushed Authorization Request (PAR) to the parameters mentioned in the specification when the connection is configured to use JWT-secured Authorization Request (JAR).

## Resolved issues

### User Enumeration in Policy Password Reset

Security PF-38628

PingFederate now prevents user enumeration in the **Policy** mode **Password Reset** flow by eliminating the observable difference between valid and invalid usernames.

### Serialized OGNL Java objects

Fixed PF-37405

We've fixed a defect that caused JSON objects using OGNL expressions included in JWT request objects sent to the OIDC provider in OIDC IdP connections not to be serialized properly.

### Kerberos realm validation error

Fixed PF-38585

We've fixed a defect that prevented PingFederate from creating, updating, or testing Kerberos realms when the `AutoGenerateKrb5Conf` parameter was set to `false` in the `com.pingidentity.common.util.KerberosConfigUtil` file.

### Authentication policy error

Fixed PF-38623

We've fixed a defect that caused an error when authentication policies with a Requested AuthN Context Authentication had **Add or Update AuthN Context Attribute** enabled.