Rapid channel changelog
Subscribe to get automatic updates. Learn more in Track rapid channel releases.
For release notes published before May 2025, refer to the Rapid channel changelog archive.
October 2025
15 Oct 2025
Versions 19379.0, 19387.0
No customer-facing features, enhancements, or fixes released.[1]
September 2025
26 Sept 2025
Version 19173.0
Key features
- Create custom authentication nodes (IAM-5759)
-
Advanced Identity Cloud lets you create your own nodes to reuse common functionality in authentication journeys. Define properties and run custom server-side scripts in these nodes to dynamically set values and decide the outcome of journeys.
Learn more in Custom nodes.
Enhancements
-
IAM-9000, IAM-9001: Add annotations and sticky notes to journeys to assist learning and collaboration.
-
IAM-9237: Allow ESVs to be embedded in URL fields for federation IdPs. This lets you set up federation IdPs with fewer ESVs because you can define a single ESV containing a UUID shared by multiple URL fields.
-
IAM-9246: Table columns are now resized uniformly across all table views.
25 Sept 2025
Version 19095.0
Key features
- Mapping custom key IDs to secrets (AME-31380)
-
You can now map custom
kidheader values for JWTs signed with the signing key to a specific ESV secret. - Nodes to support backchannel authentication journeys (AME-31636 and AME-31635)
-
The new Backchannel Initialize node and Backchannel Status node let you implement backchannel authentication from within a journey.
- Next-generation OAuth 2.0 access token modification scripts (AME-31083)
-
You can now create next-generation access token modification scripts that can use next-generation common bindings, such as
httpClient,openidm, andutils. - Ability to configure journeys as transactional only (AME-31843)
-
A transactional authentication journey only runs when Advanced Identity Cloud starts a transaction, which happens when Advanced Identity Cloud does one of the following:
-
Initializes backchannel authentication using either the
/authenticate/backchannel/initializeendpoint or the Backchannel Initialize node. -
Runs a SAML 2.0 app journey for a remote SP.
-
Runs an OAuth 2.0 app journey when Advanced Identity Cloud is acting as an authorization server.
-
Enforces a transactional authorization policy.
You can only configure transactional authentication journeys using the REST API. Set the
transactionalOnlyproperty totruein the journey configuration. -
- Journey binding for scripted nodes (OPENAM-23127)
-
The new
journeybinding for scripted nodes lets you obtain details of the current journey, including inner or child journeys.
Enhancements
-
AME-30984 and AME-30609: Enhanced authentication audit logging to include the SAML Identity Provider (IdP) and Service Provider (SP) entity IDs during SAML flows. This information lets you report on the SAML applications users are accessing, supporting analytics and dashboarding efforts.
-
AME-30985: In SAML v2.0 single sign-on (SSO) flows, the JSON web token (JWT) created in the browser’s session storage no longer expires.
The time allowed to complete the SSO flow is now determined by the configurable maximum duration of the journey session instead of the JWT expiration.
Previously, the JWT expired when the cache was cleared.
-
AME-31082 and SDKS-3681: Added support for device token refreshing to the Push Notification Service endpoint, enabling the reception of new tokens from mobile devices.
-
AME-31379: You can now enforce the OAuth 2.0 request object processing rules that apply, regardless of the request type. Create an ESV named
esv.oauth2.provider.request.object.processing.enforcedand set its value totrue. This setting forces Advanced Identity Cloud to use the specification set in the Request Object Processing Specification field of the OAuth 2.0 provider configuration for JWT requests. -
AME-31656 and AME-31468: The PingOne Protect Evaluation node has been enhanced to support dynamic risk policy IDs and target app IDs. To set the risk policy set ID dynamically, enable
Use Node State Attribute For Risk Policy Set IDin the node configuration. To set the target app ID dynamically, enableUse Node State Attribute For Target App IDin the node configuration. This instructs the node to obtain these IDs from the node state. -
AME-31398: The PingOne Protect Evaluation node has been enhanced to support custom attributes. To specify custom attributes to be used in PingOne Protect for custom predictors, set the
Node State Attribute For Custom Attributesin the node configuration. The node retrieves a map of custom attributes from the node state to be used in the evaluation request to PingOne Protect. -
AME-31487: Improvements to SAML v2.0 standalone mode include replacing legacy JSPs with URL endpoints.
You can still invoke the JSPs because they’re mapped to URLs for backward compatibility, but any customizations to these JSPs will be lost.
The following URLs supersede SAML v2.0 JSPs:
URLs
Old URL New URL /saml2/jsp/exportmetadata.jsp/ExportSamlMetadata/saml2/jsp/idpSingleLogoutInit.jsp/IDPSloInit/saml2/jsp/idpSingleLogoutRedirect.jsp/IDPSloRedirect/saml2/jsp/idpSingleLogoutPOST.jsp/IDPSloPOST/saml2/jsp/idpMNIRedirect.jsp/IDPMniRedirect/saml2/jsp/idpMNIRequestInit.jsp/IDPMniInit/saml2/jsp/idpSSOFederate.jsp/idpSSOFederate/saml2/jsp/spAssertionConsumer.jsp/Consumer/saml2/jsp/saml2AuthAssertionConsumer.jsp/AuthConsumer/saml2/jsp/spSingleLogoutInit.jsp/SPSloInit/saml2/jsp/spSingleLogoutRedirect.jsp/SPSloRedirect/saml2/jsp/spSingleLogoutPOST.jsp/SPSloPOST/saml2/jsp/spMNIRedirect.jsp/SPMniRedirect/saml2/jsp/spMNIPOST.jsp/SPMniPOST/saml2/jsp/spMNIRequestInit.jsp/SPMniInit/saml2/jsp/spSSOInit.jsp/spssoinit/saml2/jsp/idpSSOInit.jsp/idpssoinit/saml2/jsp/idpSSOFederate.jsp/idpSSOFederate/saml2/jsp/SA_IDP.jsp/idpsaehandler/saml2/jsp/SA_SP.jsp/spsaehandler -
IAM-8236: The ability to edit journeys from the AM native admin console has been removed. Use the Advanced Identity Cloud admin console to edit journeys.
-
OPENAM-20776: A new OIDC client configuration option,
Private Key JWT Audience, lets you configure and override the audience (aud) claim of a Private Key JWT. -
OPENAM-21783: Improved token management for OAuth 2.0 client applications.
This change resolves issues related to managing tokens issued to OAuth 2.0 clients that override the
Use Client-Side Access & Refresh Tokenssetting. Specifically: The /users/user/oauth2/applications endpoint now correctly returns all tokens issued to clients. Administrators can now successfully revoke any tokens issued to a client, as required. -
OPENAM-23051 and AME-31918: A new ESV,
esv.oauth2.request.object.restrictions.enforcedlets you enforce stricter adherence to the PAR and JAR specifications.Setting the value of this ESV to
trueenforces the following: The authorization server ignores authorize parameters outside therequest_uri. When sending a JWT-Secured Authorization Request (JAR), therequest_urimust be anhttpsURI. -
OPENAM-23669: _Full scopes (scopes ending in
*) can now be used by service accounts in all cases where more specific scopes (for example,:read) are used. -
OPENAM-23710: The
httpClientbinding is now available to legacy SAML 2.0 IdP adapter scripts. -
OPENAM-23850: Enhanced the PingOne Verify Evaluation node with an
Allow same device verificationoption that lets end users continue verification on their current device. -
OPENAM-23867: The LDAP Decision node no longer logs credential failures as errors. It now logs them at the
infolevel. -
OPENAM-24062: Added support for the
ECDSAalgorithm to theutils.crypto.subtlenext-generation binding. This algorithm is supported for key generation, signing, and verification.
Fixes
-
AME-31351 and AME-31471: Improvements to the Device Code flow mean that end users are now prompted to reauthenticate even when there’s an existing session for must-run and app journeys.
-
AME-31481: Validation around policy creation has been improved. If you’re using the legacy "Policy" environment condition (or a custom environment condition), you’ll need to add that to the list of allowed environment conditions for your policy set to create or update policies that use that condition type.
-
OPENAM-20749: A new ESV,
esv-enable-oauth2-sync-refresh-token-issuercauses a stateful OAuth 2.0 introspect response to overwrite theissclaim of the introspectable token. To enable this behavior, set this ESV tofalse.For compatibility reasons, the existing behavior in Advanced Identity Cloud is not changed by default.
-
OPENAM-23770: Canceling a WebAuthn flow now results in a
Client Erroroutcome, rather than an internal failure. -
OPENAM-24159: Fixed an issue that prevented multiple Identity Assertion nodes from being used in a single journey.
19 Sept 2025
Versions 19095.0, 19101.0
No customer-facing features, enhancements, or fixes released.[1]
16 Sept 2025
Version 19054.0
03 Sept 2025
Versions 18859.0, 18878.0
No customer-facing features, enhancements, or fixes released.[1]
01 Sept 2025
Version 18842.0
Key features
- Reports API endpoints to import and export report templates# (ANALYTICS-1195[2])
-
Added the ability to import and export report templates using reports API endpoints.
- Custom objects as data sources for reporting (ANALYTICS-582[2][3])
-
Custom objects can now be used as data sources for reporting. The system uses an object’s configured title for the data source name, makes its properties available as attributes, and represents all object relationships.
Enhancements
-
ANALYTICS-1165[2]: Added the capability to change a report name.
-
IAM-7547: Access policy modal now validates IPv4 or IPv6 format for IP addresses.
-
IAM-8922: The Advanced Identity Cloud admin console now accepts ESV placeholders for the following federation fields:
-
Application ID
-
Application Secret
-
Well-Known Endpoint
-
Authorization Endpoint
-
User Info Endpoint
-
Token Endpoint
-
Issuer
-
-
IAM-8982[4]: Add event function for setting the query filter/select options of a select field.
-
IAM-9066: Added Tenant Auditor option to Advanced Identity Cloud admin console federation groups claim.
-
IAM-9099, IAM-9146, IAM-9167: Many table views now support column resizing and customization.
Fixes
-
IAM-5488: Terms and Conditions now respects target attribute in anchor tags.
-
IAM-6588: The Advanced Identity Cloud admin console now correctly displays journey status for journeys disabled and enabled using ESVs.
-
IAM-8887: Prevent browsers auto-filling passwords in user registration journeys.
-
IAM-8940: Managed identity number property now accepts float values.
-
IAM-8956: Deselecting the Personal Information option now disables the section containing the user avatar in hosted account pages.
-
IAM-9169: Fixed styling for responsive table layouts with sticky action column in Identities table views.
August 2025
29 Aug 2025
Version 18823.0
Enhancements
-
FRAAS-25919: You can now use the API to configure custom domains for the Advanced Identity Cloud admin console.
-
OPENIDM-21372: Advanced Identity Cloud now prevents access to the identity repository endpoint,
/openidm/repo. This prevents uncontrolled and potentially incompatible schema changes.
Fixes
-
AME-32756: Fixed an issue with policy evaluation returning results from a stale policy index cache.
-
FRAAS-26287: Advanced Identity Cloud now correctly authenticates the sender address for emails sent to Advanced Identity Cloud tenant administrators,
saas@pingidentity.com. -
OPENDJ-11634: Advanced Identity Cloud now prevents searches with many results and no applicable index from overloading the system.
26 Aug 2025
Version N/A
Key features
- Log event exporter (FRAAS-19963)
-
Advanced Identity Cloud now lets you export log event data to an external monitoring tool, such as an OpenTelemetry-compatible SIEM or Splunk. This helps you monitor events and troubleshoot issues in near real time.
Learn more in Stream logs to an external monitoring tool.
15 Aug 2025
Versions 18678.0, 18684.0
07 Aug 2025
Versions 18559.0, 18570.0
Fixes
-
FRAAS-25821[5]: Fixed an issue that prevented IP rules in the Proxy Connect add-on from being disabled.
-
OPENAM-24159: Fixed an issue with Identity Assertion nodes failing if there are more than one in a journey.
06 Aug 2025
Version 18550.0
Enhancements
-
FRAAS-24857: CNAME verification is no longer required when creating a custom domain.
-
FRAAS-26063: You can now override the
samlErrorPageUrl. To do so, configure an ESV variable namedesv-global-saml-error-page-urland set its value to your SAML error page URL. If you don’t set this variable, Advanced Identity Cloud uses the default value of/saml2/jsp/saml2error.jsp.
July 2025
28 Jul 2025
Versions 18435.0, 18444.0
No customer-facing features, enhancements, or fixes released.[1]
21 Jul 2025
Version 18347.0, 18351.0
No customer-facing features, enhancements, or fixes released.[1]
18 Jul 2025
Version 18331.0
Key features
- Try In SDK button (IAM-8618)
-
A Try In SDK button has been added to the Details page for Native / SPA applications. This lets developers quickly test SDKs with dynamic configuration code snippets.
- Custom WS-Fed applications (IAM-8261)
-
You can now create custom WS-Fed[6] applications for single sign-on (SSO).
Enhancements
-
FRAAS-25818: The built-in SMTP server in new tenants now has a limit of 10 emails per minute and a fixed email sender address with the format
noreply@<tenant-fqdn>. -
IAM-7581: Text wrapping in table views has been improved for readability.
-
IAM-8573: IDM now includes an endpoint to retrieve individual themes from the
/themerealmconfiguration using either anIDor a_queryFilterby name. This improves performance and ensures reliable theme loading, even on slow networks. -
IAM-8610: When you create an SSO application for Microsoft 365, the application now generates a signing certificate, which you can download or rotate as needed.
-
IAM-8633: You can now add, remove, and rearrange table columns for managed identities and application provisioning tables.
-
IAM-8925[7]: In Identity Governance, you can now configure actions that trigger automatically when a form first loads or when a user changes the value of a specific field.
-
IGA-3674[7]: A Wait node is now available for IGA workflows. This node pauses the workflow until a specified date and time, for example, if you need to seek approvals.
-
IGA-3700[7]: Improved UI for suspended requests in table and request view.
-
IGA-3742[7]: The form editor now includes icons in the list of fields in the left panel.
Fixes
-
IAM-8789: Managed identity modals now correctly handle both single-value and array-based enum types.
-
IAM-4397: Fixed an issue in the hosted journey pages where the prompt text for the Choice Collector node wasn’t fully visible and the default option wasn’t visible at all.
-
IAM-8632: Fixed an issue where validation errors were incorrectly displayed for pre-populated fields.
-
IAM-8871: The hosted account pages no longer freeze and throw an error when editing details if there are empty custom enum array values.
-
IAM-8902: The application username field in SAML 2.0 NameID flows is now correctly set to
uidinstead ofusername.
16 Jul 2025
Version 18295.0
Key features
- Monitor log entries in the admin console (FRAAS-25665)
-
Advanced Identity Cloud now provides a console for monitoring log entries in development and sandbox[8] environments. You can view, filter, and search log entries for specific log sources within a timeframe to quickly identify issues, track events, and ensure system security.
01 Jul 2025
Version 18170.0
Key features
- Policy binding for next-generation scripting (AME-26150)
-
The next-generation
policybinding lets you access the policy engine API and evaluate policies from within scripts. Thepolicybinding works in a similar way to the Request policy decisions for a specific resource API call. - Set Error Details node (AME-30968)
-
The Set Error Details node adds details to the JSON response when a journey ends in an error.
Enhancements
-
AME-31372: An Agent journey is now available by default in both Alpha and Bravo realms. The
Agentjourney makes it easier to integrate with Ping Identity agents and gateways. It validates the agent credentials with an Agent Data Store Decision node. -
AME-30050: You can now enable a next-generation script in the AM admin console native console to run after a Dynamic Client Registration request is processed.
-
AME-30716: Removed
Failed to create SSO Tokenfrom logs at warning level. To observe these warnings, increase the log level to debug. -
AME-30801: The Inner Tree Evaluator node now has an optional Error Outcome that lets you capture exception details if an exception occurs during the evaluation of the child journey.
-
OPENAM-22467: Customers can now provide any value in the
typheader in JWTs. -
Greater control over journey session duration and authenticated session timeouts:
-
OPENAM-23265: The Set Session Properties node now lets you customize the Maximum Session Time and Maximum Idle Time of the session granted at the end of the journey.
-
OPENAM-23290: The new Update Journey Timeout node lets you update the timeout of the journey.
-
OPENAM-23291: The Email Suspend node now lets you configure the Suspend Duration in minutes. This duration overrides existing global or realm settings.
-
OPENAM-23515: You can now set the suspend duration in next-generation scripted decision nodes when suspending the journey.
-
-
OPENAM-23438: Following Webauthn Registration and Authentication, new information is added to the transient state.
-
OPENAM-20709: On successful authentication, the WebAuthn Authentication node now adds the UUID of the device (
webauthnDeviceUuid) and the name of the device (webauthnDeviceName) to the shared state. This lets you track the use of biometric authentication and the device used to authenticate.
Fixes
-
AME-30969: If the OIDC Claims Plugin Type in the OAuth 2.0 provider is set to
SCRIPTEDbut no script is selected, theuserinfoendpoint now returns thesubclaim, in compliance with the OIDC specification. Previously, theuserinfoendpoint returned an empty JSON object. If you still require this behavior, set theesv-scripting-legacynulloidcclaimsscriptbehaviourESV totrue. -
OPENAM-20749: For server-side OAuth 2.0 tokens, the /oauth2/introspect response can now overwrite the
issclaim of the introspectable token. To enable this behavior, set theesv-enable-oauth2-sync-refresh-token-issuerESV tofalse. -
OPENAM-22928: When agents authenticate to Advanced Identity Cloud, the session created no longer expires.
-
OPENAM-23334: You can now use the
mergeSharedandmergeTransientmethods to add nested objects toObjectAttributes. -
OPENAM-23519: Improved error handling during WebAuthn registration when the Android lock screen isn’t enabled.
Removed
- Modules and chains (AME-30762)
-
The legacy PingAM authentication mechanism using modules and chains is enabled by default in Advanced Identity Cloud but has never been supported. Modules and chains remain enabled but have been removed from the Advanced Identity Cloud admin console.
Modules and chains will be removed entirely in the near future. If you’re using them for authentication, you must migrate to nodes and trees as soon as possible.
Advanced Identity Cloud provides default journeys that replace the corresponding default modules and chains. Any default authentication processes that relied on modules and chains are unaffected by their removal.
June 2025
30 June 2025
23 Jun 2025
Version 18045.0
18 Jun 2025
Version 17994.0
Enhancements
-
FRAAS-25437: Tenant administrators with the
tenant-auditorrole can now use federated access to authenticate to Advanced Identity Cloud. -
IAM-3441: Added pagination to all list views.
-
IAM-7265: You can now right-click a node in the journey editor to access a context menu.
-
IAM-7266: Added an action bar to the journey editor that lets you deselect or delete currently selected nodes.
-
IAM-7580: Pages now span the full width of the screen, improving navigation and usability.
-
IAM-8260: Advanced Identity Cloud now supports multiple WS-Fed applications[6].
-
IAM-8640: The Release Notes link in Tenant Settings now opens the release notes for the tenant’s specific version.
-
IAM-8714[4]: You can now configure columns in the Identity Governance access review page.
-
IAM-6820: The Email Suspend node now provides a drop-down list of available email templates.
-
OPENIDM-21206[9]: Usernames and application names must now be unique, as enforced by the datastore.
Fixes
-
IAM-7413: The reCAPTCHA Enterprise node is now fully supported.
-
IAM-8489: Fixed an issue with the display of application logos in the hosted account pages.
-
IAM-8770: Fixed an issue with the calendar icon position in date fields.
-
IAM-8773: Fixed an issue where key actions such as realm login were blocked in older tenants with an unmodified original theme.
10 Jun 2025
Version 17889.0
Enhancements
-
ANALYTICS-868: The Tenant Admin Activity report has been changed to the Tenant Admin Initiated Managed Objects Changes report. The new report provides more detailed and business-friendly insights into changes made by tenant administrators:
-
Field names added, deleted, or modified.
-
Before and after values of changed attributes (if applicable).
-
Business-friendly entity name and entity type changes to custom attributes and custom objects.
-
Fixes
-
OPENAM-21783: Improved token management for OAuth 2.0 clients that override the Use Client-Side Access & Refresh Tokens setting. The OAuth 2.0 applications endpoint now correctly shows all tokens issued to these clients. Additionally, administrators can now successfully revoke any of the tokens issued to these clients.
06 Jun 2025
Version 17853.0
Enhancements
-
IAM-8405: You can now duplicate out-of-the-box reports.
-
IAM-8591: Dynamic sorting for report results. You can now sort report results directly in the Advanced Identity Cloud admin console after running a report.
-
Sorting is available only when the result set contains fewer than 10,000 rows.
-
Columns with complex data types (for example, JSON) can’t be sorted.
-
Downloaded reports reflect the original data order, not the sorted view from the Advanced Identity Cloud admin console.
-
06 Jun 2025
Version 17836.0
Fixes
-
FRAAS-25269: The IDC.CLI OAuth 2.0 client is now deprecated in existing tenants and no longer provisioned in new tenants. Use a service account instead.
03 Jun 2025
Versions 17804.0, 17821.0
No customer-facing features, enhancements, or fixes released.[1]
May 2025
30 May 2025
Version 17779.0
Key features
- Tenant auditors (IAM-8086)
-
Advanced Identity Cloud now lets you invite tenant auditors to access the Advanced Identity Cloud admin console. Tenant auditors can view settings, configuration, and data but cannot modify them.
- Tenant auditor role (FRAAS-24460)
-
Advanced Identity Cloud now supports a tenant auditor role with read-only access to ancillary APIs.
For new tenants, Advanced Identity Cloud doesn’t support non-global realm user access and OAuth2 client access to the ESV API. Access is deprecated for existing tenants.
23 May 2025
Versions 17709.0, 17713.0
Enhancements
-
FRAAS-25205: Consolidated
End User UI,Login UI,Administrator Registration UI, andAdministrator UIstatus page components into a singleAdministrator UIcomponent as they were all reporting the same service. -
OPENIDM-15771: You can now set locales in identity management scripts with the
_localeparameter. -
OPENIDM-17680: Advanced Identity Cloud now supports enumerations in string and number attributes of its identity schema. To make an attribute an enumeration, add
"enum" : [ "one", "two", "three" ]to the attribute. Advanced Identity Cloud requires create and update privileges to use one of the enumerated values. -
OPENIDM-19918: You can now choose whether synchronization detects identity array changes using _ordered or unordered comparisons. Set the
comparisonconfiguration property in the schema. Unordered JSON array comparison ignores the order of elements and can negate the need for certain custom scripts within mappings. Relationship and virtual property array fields default to unordered comparisons. All other fields default to ordered comparisons. -
OPENIDM-20023: RCS communication with Advanced Identity Cloud can now use stricter authorization. Learn more in Secure RCS access and Migration dependent features.
21 May 2025
Version 17680.0
Fixes
-
FRAAS-25256: Fixed an issue that was causing missing data in analytics dashboards.
-
OPENIDM-20995: Fixed an issue that prevented error reports during certain operations on groups or users. For example trying to remove a non-existing attribute or null value now correctly results in an exception message to the client if these operations are not supported by the target system.
13 May 2025
Versions 17581.0, 17584.0
No customer-facing features, enhancements, or fixes released.[1]
08 May 2025
Versions 17546.0, 17549.0
Enhancements
-
ANALYTICS-1004[3]: Support for custom attributes and relationships in the organization entity for advanced reports.
06 May 2025
Versions 17513.0, 17514.0
No customer-facing features, enhancements, or fixes released.[1]