<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
    <channel>
        <title>Release Notes | PingCentral</title>
        <link>https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html</link>
        <description>Release Notes</description>
        <lastBuildDate>Fri, 25 Sep 2026 18:27:14 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <ttl>5</ttl>
        <copyright>Copyright 2026 Ping Identity. All rights reserved.</copyright>
        <item>
            <title><![CDATA[PingCentral 3.2 (September 2026)]]></title>
            <link>https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#pingcentral-3-2-september-2026</link>
            <guid isPermaLink="false">https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#pingcentral-3-2-september-2026</guid>
            <pubDate>Wed, 04 Mar 2026 12:00:00 GMT</pubDate>
            <description><![CDATA[

<div class="sectionbody">
<div class="sect2">
<h3 id="enhanced-frontend-javascript-protection"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#enhanced-frontend-javascript-protection"></a>Enhanced frontend JavaScript protection</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-1988</span></p>
</div>
<div class="paragraph">
<p>Improved protection for PingCentral frontend JavaScript assets by adding additional obfuscation.</p>
</div>
</div>
<div class="sect2">
<h3 id="full-expression-names-in-the-expression-dropdown"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#full-expression-names-in-the-expression-dropdown"></a>Full expression names in the Expression dropdown</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-5930</span></p>
</div>
<div class="paragraph">
<p>Added a hover help hint to the <strong class="uicontrol">Expression</strong> dropdown. When an expression name is truncated, hovering over it now displays the full name.</p>
</div>
</div>
<div class="sect2">
<h3 id="required-indicators-for-saml-attribute-mappings"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#required-indicators-for-saml-attribute-mappings"></a>Required indicators for SAML attribute mappings</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-6544</span></p>
</div>
<div class="paragraph">
<p>Fixed an issue in which SAML attribute-mapping fields imported from metadata were not marked as required. Unfulfilled attributes are now highlighted, making it clear which fields must be completed before the application can be saved.</p>
</div>
</div>
<div class="sect2">
<h3 id="improved-swagger-validation-feedback"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#improved-swagger-validation-feedback"></a>Improved Swagger validation feedback</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-6559</span></p>
</div>
<div class="paragraph">
<p>Invalid JSON payloads no longer silently disable the <strong class="uicontrol">Execute</strong> button. Users can now submit the request and receive an appropriate error message.</p>
</div>
</div>
<div class="sect2">
<h3 id="simplified-oauth-client-setup"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#simplified-oauth-client-setup"></a>Simplified OAuth client setup</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-6726</span></p>
</div>
<div class="paragraph">
<p>Removed the unnecessary OAuth/OIDC radio-button choice when adding an OAuth client as a managed application. PingCentral now determines the client type from the PingFederate API payload, simplifying the setup experience.</p>
</div>
</div>
<div class="sect2">
<h3 id="eula-acceptance-configuration-updates"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#eula-acceptance-configuration-updates"></a>EULA acceptance configuration updates</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-7004</span></p>
</div>
<div class="paragraph">
<p>Updated the PingCentral BRASS image to honor the <code>PING_IDENTITY_ACCEPT_EULA=YES</code> environment variable. When enabled, the license agreement screen is skipped during startup and no longer requires manual EULA acceptance.</p>
</div>
</div>
<div class="sect2">
<h3 id="improved-resilience-against-socket-exhaustion"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#improved-resilience-against-socket-exhaustion"></a>Improved resilience against socket exhaustion</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-7014</span></p>
</div>
<div class="paragraph">
<p>Improved PingCentral’s resilience against socket-exhaustion conditions. Server-side timeouts now close idle connections and bound outbound metadata requests, while URL validation reject disallowed targets, helping keep the service responsive under excessive connection or request load.</p>
</div>
</div>
<div class="sect2">
<h3 id="sanitized-api-validation-errors"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#sanitized-api-validation-errors"></a>Sanitized API validation errors</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-7047</span></p>
</div>
<div class="paragraph">
<p>Sanitized PingCentral API validation errors to prevent stack traces and internal implementation details from being returned in API responses. Users now receive a concise error message, while detailed diagnostics remain available in the server logs.</p>
</div>
</div>
<div class="sect2">
<h3 id="rsa-key-messaging-clarified"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#rsa-key-messaging-clarified"></a>RSA key messaging clarified</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-7090</span></p>
</div>
<div class="paragraph">
<p>PingCentral only accepts RSA keys for server and client TLS key pairs, and importing an elliptic-curve (EC) key used to cause a server error. Now, users receive a message stating that EC keys are not supported.</p>
</div>
</div>
<div class="sect2">
<h3 id="improved-client-secret-validation-for-saml-applications"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#improved-client-secret-validation-for-saml-applications"></a>Improved client-secret validation for SAML applications</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-7137</span></p>
</div>
<div class="paragraph">
<p>Improved error handling for requests to retrieve a client secret for a SAML application. The <code>/api/v1/applications/clientSecret/{applicationId}/{environmentId}</code> endpoint now returns a validation error with a message stating that client secrets are not applicable to SAML_20_SP applications.</p>
</div>
</div>
<div class="sect2">
<h3 id="fixed-intermittent-startup-failure"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#fixed-intermittent-startup-failure"></a>Fixed intermittent startup failure</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7161</span></p>
</div>
<div class="paragraph">
<p>Fixed an issue that intermittently prevented PingCentral 3.1 from starting on Java 17 or Java 21.</p>
</div>
</div>
<div class="sect2">
<h3 id="updated-bc-fips-security-library"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#updated-bc-fips-security-library"></a>Updated bc-fips security library</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-7165</span></p>
</div>
<div class="paragraph">
<p>Updated the bc-fips security library to version 2.1.2 to address possible vulnerabilities. You can find more information about the <a href="https://nvd.nist.gov/vuln/search?keyword=CVE-2025-8885&amp;resultType=records" target="_blank" rel="noopener">CVE-2025-8885</a> vulnerability on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect2">
<h3 id="updated-pingcommons-bc-fips-security-libraries"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#updated-pingcommons-bc-fips-security-libraries"></a>Updated pingcommons-bc-fips security libraries</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-7166</span></p>
</div>
<div class="paragraph">
<p>Updated the <code>pingcommons-bc-fips</code> dependencies to fixed versions, including <code>bcpkix-fips</code> 2.0.8 and <code>bc-fips</code> 2.1.2. You can find more information about the <a href="https://nvd.nist.gov/vuln/search?keyword=CVE-2025-8916&amp;resultType=records" target="_blank" rel="noopener">CVE-2025-8916</a> vulnerability on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect2">
<h3 id="corrected-license-validation-api-documentation"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#corrected-license-validation-api-documentation"></a>Corrected license validation API documentation</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7171</span></p>
</div>
<div class="paragraph">
<p>Updated the Swagger documentation for POST <code>/api/v1/license/validate</code> to help API users submit license validation requests using the supported request format.</p>
</div>
</div>
<div class="sect2">
<h3 id="updated-commons-lang3-security-dependency"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#updated-commons-lang3-security-dependency"></a>Updated commons-lang3 security dependency</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-7173</span></p>
</div>
<div class="paragraph">
<p>Updated the <code>pingcommons</code> and <code>commons-lang3</code> dependencies and upgraded <code>commons-lang3</code> to version 3.20.0. You can find more information about the <a href="https://nvd.nist.gov/vuln/search?keyword=CVE-2025-48924&amp;resultType=records" target="_blank" rel="noopener">CVE-2025-48924</a> vulnerability on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect2">
<h3 id="updated-json-path-security-dependency"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#updated-json-path-security-dependency"></a>Updated json-path security dependency</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-7175</span></p>
</div>
<div class="paragraph">
<p>Updated all declared json-path dependencies to non-vulnerable versions. You can find more information about the <a href="https://nvd.nist.gov/vuln/search?keyword=CVE-2023-51074&amp;resultType=records" target="_blank" rel="noopener">CVE-2023-51074</a> vulnerability on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect2">
<h3 id="removed-vulnerable-transitive-logging-dependencies"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#removed-vulnerable-transitive-logging-dependencies"></a>Removed vulnerable transitive logging dependencies</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7177</span></p>
</div>
<div class="paragraph">
<p>Updated dependency configuration in the <code>pass-common</code> and <code>pass-jpa-entity</code> modules to exclude transitive spring-boot-starter-logging dependencies, preventing vulnerable Logback components from being included. You can find more information about the <a href="https://nvd.nist.gov/vuln/search?keyword=CVE-2025-11226&amp;resultType=records" target="_blank" rel="noopener">CVE-2025-11226</a> and <a href="https://nvd.nist.gov/vuln/search?keyword=CVE-2026-1225&amp;resultType=records" target="_blank" rel="noopener">CVE-2026-1225</a> vulnerabilities on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect2">
<h3 id="preserve-extended-properties-during-promotion"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#preserve-extended-properties-during-promotion"></a>Preserve extended properties during promotion</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7205</span></p>
</div>
<div class="paragraph">
<p>Applications created from templates created before PingCentral 3.0, or from templates that have not yet been synchronized, could appear without extended properties in PingCentral. Promoting those applications could unintentionally overwrite extended properties that were already configured in PingFederate.</p>
</div>
<div class="paragraph">
<p>Promotion now preserves existing extended properties when the application has no extended properties configured. The fix applies to both PingFederate clients and SAML connections.</p>
</div>
<div class="admonitionblock note">
<table>
<tbody><tr>
<td class="icon">
<i class="fa icon-note" title="Note"></i>
</td>
<td class="content">
After upgrading, synchronize existing templates and update their applications before using the extended properties configuration. New extended properties also require a template sync and application update before they appear in the application.
</td>
</tr>
</tbody></table>
</div>
</div>
<div class="sect2">
<h3 id="oauth-and-oidc-template-loading"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#oauth-and-oidc-template-loading"></a>OAuth and OIDC template loading</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7208</span></p>
</div>
<div class="paragraph">
<p>After upgrading to version 3.1.0, templates for OIDC and OAuth clients could lose their template association in the admin console, even when the underlying PingFederate OIDC policies were valid. Loading a template could fail with an <code>Unable to retrieve</code> error when older template revisions did not contain expected OIDC policy attributes.</p>
</div>
<div class="paragraph">
<p>Template retrieval now handles older revision data correctly, allowing OIDC and OAuth client templates to render as expected.</p>
</div>
</div>
<div class="sect2">
<h3 id="more-client-configuration-options-during-promotion"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#more-client-configuration-options-during-promotion"></a>More client configuration options during promotion</h3>
<div class="paragraph">
<p><span class="ping_changetype-improved">Improved</span>
<span class="ping_ticket">PASS-7209</span></p>
</div>
<div class="paragraph">
<p>Previously, application owners had to edit the promotion JSON to configure client-specific values for OAuth and OIDC applications.</p>
</div>
<div class="paragraph">
<p>PingCentral now lets application owners configure additional client settings during promotion, including the client ID, JWKS URL, and the signing algorithm, providing a more streamlined experience.</p>
</div>
</div>
<div class="sect2">
<h3 id="customize-ognl-expressions-with-application-specific-values"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#customize-ognl-expressions-with-application-specific-values"></a>Customize OGNL expressions with application-specific values</h3>
<div class="paragraph">
<p><span class="ping_changetype-new">New</span>
<span class="ping_ticket">PASS-7213</span></p>
</div>
<div class="paragraph">
<p>Previously, administrators had to create multiple trusted expressions or manually update OGNL expressions in PingFederate when applications required small variations.</p>
</div>
<div class="paragraph">
<p>PingCentral now supports placeholders in OGNL expressions. Administrators can define the portions of an expression that application developers can customize, and input validation can restrict values to approved characters, simplifying application promotion while maintaining control over the expression.</p>
</div>
</div>
<div class="sect2">
<h3 id="application-editing-and-save-failures"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#application-editing-and-save-failures"></a>Application editing and save failures</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7220</span></p>
</div>
<div class="paragraph">
<p>Starting with version 3.1.1, OAuth and OIDC application data could be corrupted when an application was edited and saved through the admin console. The <strong class="uicontrol">Applications</strong> page then displayed a white screen, and the application could not be managed normally.</p>
</div>
<div class="paragraph">
<p>This PostgreSQL-specific issue has been resolved.</p>
</div>
</div>
<div class="sect2">
<h3 id="removed-unlicensed-font-reference"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#removed-unlicensed-font-reference"></a>Removed unlicensed font reference</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7221</span></p>
</div>
<div class="paragraph">
<p>Version 3.1.1 referenced the Proxima Nova font family, which is not licensed for Ping Identity to use. The UI library was updated to remove this reference.</p>
</div>
</div>
<div class="sect2">
<h3 id="sanitized-certificate-upload-validation-errors"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#sanitized-certificate-upload-validation-errors"></a>Sanitized certificate-upload validation errors</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7224</span></p>
</div>
<div class="paragraph">
<p>Improved certificate-upload validation to prevent SQL statements and other technical details from appearing in API error responses. Malformed certificates now return a standard validation message, while detailed diagnostics remain available to administrators in server-side logs.</p>
</div>
</div>
<div class="sect2">
<h3 id="white-screen-after-saving-oauth-or-oidc-templates-and-applications"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#white-screen-after-saving-oauth-or-oidc-templates-and-applications"></a>White screen after saving OAuth or OIDC templates and applications</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7226</span></p>
</div>
<div class="paragraph">
<p>Previously, when users added and saved an OAuth or OIDC template or application in PingCentral, the admin console could display a white screen because the CSS file failed to load, even though the template or application was saved successfully.</p>
</div>
<div class="paragraph">
<p>This issue has been resolved. OAuth and OIDC templates and applications now save and display correctly in the admin console.</p>
</div>
</div>
<div class="sect2">
<h3 id="pingfederate-application-number-chip-display"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#pingfederate-application-number-chip-display"></a>PingFederate application number chip display</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7227</span></p>
</div>
<div class="paragraph">
<p>Fixed an issue in which the PingFederate application number chip displayed <code>N/A</code> when PingFederate was verified. The chip now displays the number of applications and connections that the environment contains.</p>
</div>
</div>
<div class="sect2">
<h3 id="available-environment-list-issue"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#available-environment-list-issue"></a>Available environment list issue</h3>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7228</span></p>
</div>
<div class="paragraph">
<p>We’ve fixed an issue in which selecting a verified environment from the list of available environments could retrieve data from a different, unverified environment. Promotion operations now load data from the environment selected by the user as expected.</p>
</div>
</div>
</div>
]]></description>
        </item>
        <item>
            <title><![CDATA[Previous Releases]]></title>
            <link>https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#previous-releases</link>
            <guid isPermaLink="false">https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#previous-releases</guid>
            <pubDate>Tue, 31 Jan 2023 12:00:00 GMT</pubDate>
            <description><![CDATA[

<div class="sectionbody">
<div class="paragraph">
<p>Release notes for previous releases are available here.</p>
</div>
<div class="sect2 2025-03-27T12:00:00Z">
<h3 id="pingcentral-3-1-march-2026"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#pingcentral-3-1-march-2026"></a>PingCentral 3.1 (March 2026)</h3>
<div class="sect3">
<h4 id="administrators-can-now-configure-signature-policies-for-saml-sp-connections"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#administrators-can-now-configure-signature-policies-for-saml-sp-connections"></a>Administrators can now configure signature policies for SAML SP connections</h4>
<div class="paragraph">
<p><span class="ping_changetype-improved">New</span>
<span class="ping_ticket">PASS-7155</span></p>
</div>
<div class="paragraph">
<p>Administrators can now configure signature policies for SP connections when they create templates and applications, and promote applications to PingCentral environments.</p>
</div>
<div class="paragraph">
<p>Previously, PingFederate administrators had to configure the signature policies after the applications were promoted to PingFederate, which interrupted their workflow and caused unnecessary delays in the process.</p>
</div>
<div class="paragraph">
<p>Note that signature policy configurations are only visible if the corresponding profiles and artifact binding are enabled in the underlying PingFederate SP connection. To learn more, refer to step 8 in <a href="https://docs.pingidentity.com/pingcentral/3.2/pingcentral_for_iam_administrators/pingcentral_mng_templates/pingcentral_mng_templates.html#_adding_saml_application_templates" class="xref page">Adding SAML application templates</a>.</p>
</div>
</div>
<div class="sect3">
<h4 id="security-vulnerability-fixed"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#security-vulnerability-fixed"></a>Security vulnerability fixed</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-1323</span></p>
</div>
<div class="paragraph">
<p>We’ve fixed the client-side security vulnerability in DOM-based XSS in redirect URI definitions.</p>
</div>
</div>
<div class="sect3">
<h4 id="apache-commons-compress-updated"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#apache-commons-compress-updated"></a>Apache Commons Compress updated</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-5852</span></p>
</div>
<div class="paragraph">
<p>The Apache Commons Compress has been updated to version 1.26, which resolved the security vulnerability that affected versions 1.0 to 1.21. You can find more information about the <a href="https://nvd.nist.gov/vuln/detail/cve-2021-36090">CVE-2021-36090 vulnerability</a> on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect3">
<h4 id="moment-js-updated"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#moment-js-updated"></a>Moment.js updated</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-6410</span></p>
</div>
<div class="paragraph">
<p>Moment.js has been updated to version 2.29.4, which resolved the path traversal vulnerability that affected versions 1.0.1 to 2.29.1. You can find more information about the <a href="https://nvd.nist.gov/vuln/detail/cve-2022-24785">CVE-2022-24785 vulnerability</a> on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect3">
<h4 id="option-to-download-saml-idp-metadata-issue-fixed"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#option-to-download-saml-idp-metadata-issue-fixed"></a>Option to download SAML IdP metadata issue fixed</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7017</span></p>
</div>
<div class="paragraph">
<p>We’ve fixed the <strong class="uicontrol:">Promotion Details</strong> page so that it now displays the option to download the SAML IdP metadata if the application was promoted directly from the JSON file.</p>
</div>
</div>
<div class="sect3">
<h4 id="swagger-ui-library-updated"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#swagger-ui-library-updated"></a>Swagger UI library updated</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7021</span></p>
</div>
<div class="paragraph">
<p>The Swagger UI library has been updated from version 2.9.2 to 3.23.11 to prevent future false-positive scan alerts. You can find more information about the <a href="https://nvd.nist.gov/vuln/detail/cve-2019-17495">CVE-2019-17495 vulnerability</a> on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect3">
<h4 id="swagger-json-fixed"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#swagger-json-fixed"></a>Swagger.json fixed</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7132</span></p>
</div>
<div class="paragraph">
<p>We’ve fixed the swagger.json endpoint, and it now returns information about the Admin API as expected.</p>
</div>
</div>
<div class="sect3">
<h4 id="api-loading-issues-resolved"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#api-loading-issues-resolved"></a>API loading issues resolved</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7163</span></p>
</div>
<div class="paragraph">
<p>We’ve fixed the issue where users encountered a continuous loading screen when they tried to access the API. The API now works as expected and returns a response.</p>
</div>
</div>
<div class="sect3">
<h4 id="h2-database-updated"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#h2-database-updated"></a>H2 database updated</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7070</span></p>
</div>
<div class="paragraph">
<p>The H2 database has been updated to version 2.2.220, which resolved the security vulnerability that affected version 2.1.210. You can find more information about the <a href="https://nvd.nist.gov/vuln/detail/cve-2022-45868">CVE-2022-45868 vulnerability</a> on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect3">
<h4 id="hibernate-library-updated"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#hibernate-library-updated"></a>Hibernate library updated</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7172</span></p>
</div>
<div class="paragraph">
<p>The <code class="filepath">hibernate-ehcache</code> library is no longer used, which resolved the security vulnerability. You can find more information about the <a href="https://nvd.nist.gov/vuln/detail/CVE-2026-0603">CVE-2026-0603 vulnerability</a> on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect3">
<h4 id="socket-appender-in-apache-log4j-updated"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#socket-appender-in-apache-log4j-updated"></a>Socket Appender in Apache Log4j updated</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7174</span></p>
</div>
<div class="paragraph">
<p>The Socket Appender in Apache Log4j has been updated to version 2.25.3, which resolved the security vulnerability that affected versions 2.0-beta9 through 2.25.2. You can find more information about the <a href="https://nvd.nist.gov/vuln/detail/CVE-2025-68161">CVE-2025-68161 vulnerability</a> on the National Vulnerability Database site.</p>
</div>
</div>
<div class="sect3">
<h4 id="sso-issue-resolved"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#sso-issue-resolved"></a>SSO issue resolved</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7176</span></p>
</div>
<div class="paragraph">
<p>We’ve fixed an issue with SSO, and users are now redirected to the PingFederate sign-on page instead of the PingCentral home page when they sign on.</p>
</div>
</div>
<div class="sect3">
<h4 id="outdated-uri-issue-resolved"><a class="anchor" href="https://docs.pingidentity.com/pingcentral/3.2/release_notes/pingcentral_relnotes_home.html#outdated-uri-issue-resolved"></a>Outdated URI issue resolved</h4>
<div class="paragraph">
<p><span class="ping_changetype-fixed">Fixed</span>
<span class="ping_ticket">PASS-7187</span></p>
</div>
<div class="paragraph">
<p>We’ve fixed an issue where redirect URIs were still displayed in OAuth or OIDC applications after the environment referenced in the URI was deleted.</p>
</div>
</div>
</div>
</div>
]]></description>
        </item>
    </channel>
</rss>