---
title: PingAuthorize 10.1.0.2 (September 2024)
description: New
component: pingauthorize
version: 10.1
page_id: pingauthorize:release_notes:paz_rn_10102
canonical_url: https://docs.pingidentity.com/pingauthorize/10.1/release_notes/paz_rn_10102.html
revdate: September 26, 2024
section_ids:
  added-a-new-policy-query-response-view: Added a new policy query response view
  added-policy-query-debug-logging: Added policy query debug logging
  added-support-for-mapped-diagnostic-context: Added support for Mapped Diagnostic Context
  added-support-for-a-new-signature-algorithm: Added support for a new signature algorithm
  improved-policy-query-error-handling: Improved policy query error handling
  improved-resolution-of-query-attributes: Improved resolution of query attributes
  fixed-an-issue-with-policy-query-api-responses: Fixed an issue with Policy Query API responses
  fixed-an-issue-with-the-decision-visualizer: Fixed an issue with the Decision Visualizer
  fixed-a-memory-leak-issue: Fixed a memory leak issue
  fixed-an-issue-with-config-diff: Fixed an issue with config-diff
---

# PingAuthorize 10.1.0.2 (September 2024)

## Added a new policy query response view

New

We added support for a new `unfiltered` policy query response view. This view includes every decision used to compose the final query response, regardless of the outcome or the presence of statements. Learn more in [Configuring query response granularity](../pingauthorize_policy_administration_guide/paz_troubleshooting_policy_queries.html#configure_query_response_granularity).

## Added policy query debug logging

New

We added debugging capabilities for policy query audit logging. Enabling the `DEBUG` log level brings enhanced visibility to the attribute data and decision logic underlying query responses. Learn more in [Troubleshooting policy queries](../pingauthorize_policy_administration_guide/paz_troubleshooting_policy_queries.html#policy_query_logging).

## Added support for Mapped Diagnostic Context

New

We added support for Mapped Diagnostic Context (MDC) capabilities in logging. MDC enriches log messages with additional request context, enabling you to diagnose issues across application components. Learn more in [Enabling Mapped Diagnostic Context for Policy Editor logs](../pingauthorize_server_administration_guide/paz_pe_mdc_logging.html).

## Added support for a new signature algorithm

New

We added support for Elliptic Curve Digital Signature Algorithm (ECDSA)-encoded signatures for JWT tokens when using the `Has Valid Signature For JWKS` and `Has Invalid Signature For JWKS` attribute comparators. Learn more in [Conditions](../pingauthorize_policy_administration_guide/paz_conditions.html).

## Improved policy query error handling

Improved

We improved and standardized error handling for requests sent to the `governance-engine/query` endpoint.

## Improved resolution of query attributes

Improved

When making a policy query request, you might want to use a single-valued attribute to resolve a `query` attribute. Now, you can include this single-valued attribute in the `query` section, rather than the `context` section of the request.

## Fixed an issue with Policy Query API responses

Fixed PAZ-12752

We fixed an issue where the same request sent to the `governance-engine/query` endpoint could produce inconsistent responses.

## Fixed an issue with the Decision Visualizer

Fixed PAZ-11767

We fixed an issue where pasting an audit log entry without the `decisionTree` or `evaluationLog` field into the Decision Visualizer would incorrectly return a `Cannot read properties of undefined (reading 'create')` error in addition to a `decisionTree or evaluationLog must be enabled to visualize decision tree` error.

## Fixed a memory leak issue

Fixed PAZ-13013

We fixed an issue where, when using the PingAuthorize Server's API security gateway in embedded PDP mode, policy decision logging could cause a memory leak and negatively impact the performance of long-running server instances.

## Fixed an issue with `config-diff`

Fixed DS-49071

We fixed an issue where `config-diff` would result in an `Unknown property` error when comparing configuration objects of different types.