Rapid channel changelog
Subscribe to get automatic updates: Rapid channel changelog RSS feed
For release notes published before December 2024, refer to the Rapid channel changelog archive.
September 2025
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-8687: The PingOne Verification node now supports same device verification by letting you configure a Continue on this device? button.
-
IAM-8922: The Advanced Identity Cloud admin console now accepts ESV placeholders for the following federation fields:
-
Authorization Endpoint
-
Well-Known Endpoint
-
Token Endpoint
-
Issuer
-
-
IAM-8982[4]: Add event function for setting the query filter/select options of a select field.
-
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-9066: Added Tenant Auditor option to Advanced Identity Cloud admin console federation groups claim.
-
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 Export log events 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-url
and 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
/themerealm
configuration using either anID
or a_queryFilter
by 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
uid
instead 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
policy
binding lets you access the policy engine API and evaluate policies from within scripts. Thepolicy
binding 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
Agent
journey 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 Token
from 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
typ
header 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
SCRIPTED
but no script is selected, theuserinfo
endpoint now returns thesub
claim, in compliance with the OIDC specification. Previously, theuserinfo
endpoint returned an empty JSON object. If you still require this behavior, set theesv-scripting-legacynulloidcclaimsscriptbehaviour
ESV totrue
. -
OPENAM-20749: For server-side OAuth 2.0 tokens, the /oauth2/introspect response can now overwrite the
iss
claim of the introspectable token. To enable this behavior, set theesv-enable-oauth2-sync-refresh-token-issuer
ESV tofalse
. -
OPENAM-22928: When agents authenticate to Advanced Identity Cloud, the session created no longer expires.
-
OPENAM-23334: You can now use the
mergeShared
andmergeTransient
methods 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-auditor
role 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 UI
status page components into a singleAdministrator UI
component as they were all reporting the same service. -
OPENIDM-15771: You can now set locales in identity management scripts with the
_locale
parameter. -
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
comparison
configuration 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]
April 2025
28 Apr 2025
Versions 17434.0, 17436.0
No customer-facing features, enhancements, or fixes released.[1]
23 Apr 2025
Version 17384.0
Enhancements
-
IAM-987: Added support for enums (drop-down lists) to hosted account pages.
-
IAM-1116: Added support for enums (drop-down lists) to the Advanced Identity Cloud admin console.
-
IAM-2103: Added support for enums (drop-down lists) to hosted journey pages.
-
IAM-6822: Added the ability to manage cookie domains in the Advanced Identity Cloud admin console.
-
IAM-7412: Updated the password policy feature in the Advanced Identity Cloud admin console. Added the ability to specify a minimum substring length between 3 - 64 to use when validating passwords against user attribute values. The default is still 5 characters, but can now be reduced to as few as 3 characters to catch shorter string matches.
-
IAM-7794[4]: Added support for using custom identity objects in the form builder.
-
IAM-7919: Improved color contrast ratio of the Delete Account button text when focused.
-
IAM-7934: Improved color contrast ratio of date fields when focused.
-
IAM-7957: Improved color contrast ratio of the Deselect button text when focused.
-
IAM-7966: Improved color contrast ratio of In Progress text.
-
IAM-8016[4]: Allow form authors to specify a user filter when dynamic enums are selected.
-
IAM-8085: Updated the Add a Parameter reports modal to use entity attributes for input.
Fixes
-
FRAAS-15518: Fixed issue that prevented localization of Session timed out message in certain locales.
-
IAM-5834: Fixed a double-encoding issue in the SAML app that affected IdP-initiated sign on.
-
IAM-6796: Jobs are now prevented from being scheduled with frequencies that cause invalid date errors.
-
IAM-7855: Fixed a typo in the help text returned when there are no results to display.
-
IAM-8237: Corrected floating labels in the date picker in the hosted journey pages.
-
IAM-8361: The Save button in the Edit Bookmark application is now inactive while checking if the ESV exists.
-
IAM-8364: Fixed issues in SAML end-to-end scenarios.
-
IAM-8378: Fixed an issue that stripped HTML elements from email templates.
-
IAM-8403: Fixed border focus location and floating label issues in Tag fields.
-
IAM-8434: Fixed an issue that prevented duplication of new themes that contain special characters.
16 Apr 2025
Versions 17283.0, 17299.0
No customer-facing features, enhancements, or fixes released.[1]
08 Apr 2025
Versions 17178.0, 17186.0
Enhancements
-
OPENDJ-11175: The password validation mechanism has been enhanced to include checks for attribute values shorter than the
min-substring-length
(the default is 5).For example, if the password contains
Bob
for a user named Bob, the password is rejected, even ifmin-substring-length
is set to 5.
March 2025
28 Mar 2025
Versions 17072.0, 17079.0
Enhancements
-
ANALYTICS-846: You can now select the attribute type and value for report entity attributes.
-
ANALYTICS-983[3]: You can now use regular expression operators in Advanced Reporting.
21 Mar 2025
Key Features
- Custom attributes for user entity in Advanced Reports (ANALYTICS-863)[3][10]
-
When a tenant administrator modifies the
users
identity object from the native console and adds a new custom attribute, the attribute is immediately available on the Create Report page. Administrators can use the custom attribute for their reports and filters.Learn more in Custom attributes for user objects.
20 Mar 2025
Versions 17002.0, 17015.0
No customer-facing features, enhancements, or fixes released.[1]
19 Mar 2025
Versions 16981.0, 16989.0
No customer-facing features, enhancements, or fixes released.[1]
17 Mar 2025
Version 16940.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.
Enhancements
-
IAM-6996: Added the ability to create a specific OAuth 2.0 client when creating a connector server, rather than relying on the default RCSClient.
-
IAM-7109: You can now use an ESV to set the From Address in the email provider configuration.
-
IAM-7827/ANALYTICS-835[3]: In the analytics report editor in Advanced Reporting, you can now reorder columns by dragging and dropping them.
-
IAM-7841/ANALYTICS-840[3]: The reports page in Advanced Reporting is now a list view with pagination and search.
-
IAM-8321: In the journey editor, the node titles now wrap within the left nodes panel.
13 Mar 2025
Version 16885.0, 16887.0
No customer-facing features, enhancements, or fixes released.[1]
February 2025
27 Feb 2025
Version 16747.0
Key Features
- Flow Control node (AME-30017)
-
You can now randomly direct users down different journey paths. Learn more in Flow Control node.
- OIDC application journeys (AME-28650)
-
You can now configure OAuth 2.0 / OIDC client applications to redirect authentication requests to a specified journey. Learn more in Redirect an OAuth 2.0 or OIDC client application to a journey.
Enhancements
-
AME-27705: Extend the
utils
binding for all next-generation scripts to support low-level cryptographic operations. These operations include encryption, decryption, hashing, signing, verification, and key generation.Find more information in Perform low-level cryptographic operations in next-generation scripts.
-
AME-28780: Added an IDM policy condition that can assert conditions against an IDM resource type such as user identities.
-
AME-28954: Modified the import metadata endpoint to support updating signing and encryption certificates for existing SAML service providers (SPs) without requiring the deletion or recreation of SP configurations.
-
AME-29307: You can now use DER-encoded certificates for OAuth 2.0 client authentication.
-
AME-29810: The realm default authentication service can no longer be a journey with
mustRun
enabled. Also,mustRun
can no longer be enabled on journeys that are set as the realm default authentication service. -
AME-29835: Configuration Provider Node scripts can now use the next-generation scripting engine, which gives them access to common bindings such as
openidm
andhttpClient
. -
AME-30076: New
getApplicationId()
method provides a consistent way to retrieve the application ID from both SAML and OAuth 2.0 applications.
Fixes
-
AME-29504: The
scriptName
andlogger
bindings in library scripts referenced the same default script name and ID. Their previous behavior has now been restored by inheriting values from the referencing script. -
AME-29965: The Configuration Provider node now works with the Inner Tree Evaluator for nested inner journeys.
-
AME-30377: The following two warning level log messages have been reduced to debug level because they’re rarely useful and appear frequently, drowning out more useful log entries:
-
No users have been identified.
-
Ignoring the new universal id as that is empty and the current universal id is already set.
-
-
OPENAM-22120: Back-channel logout tokens now include the
exp
claim. -
OPENAM-23077: The
access_token
endpoint now responds with the correct error code when thecode_verifier
isn’t supplied (for example,invalid_grant
).
20 Feb 2025
Version 16676.0
Key features
- Advanced sync (IAM-8090)
-
Many of the mapping synchronization features available in the IDM admin console are now exposed in the Advanced Sync tab when viewing an application. You can create additional mappings between applications or between applications and identity profiles.
Enhancements
-
IAM-7967[4]: Added an image description for the approvals Low Priority icon.
-
IAM-7977: Improved the font color contrast ratio of the email address displayed in Advanced Identity Cloud admin console user profiles.
-
IAM-8053: The Advanced Identity Cloud end-user UI can now use
defaultText
value as a fallback value when the actual value of a field returns empty. -
OPENIDM-20139: Applications can now use
postAction
scripts for theONBOARD
action.
Fixes
-
IAM-7719[4]: Users are now redirected back to the compliance Policy Rules tab after creating or editing a policy rule.
04 Feb 2025
Version 16508.0
Enhancements
-
IAM-4692: Managed identity boolean fields now use a checkbox instead of a toggle.
-
IAM-6581: SAML 2.0 application journeys can now be configured in the Advanced Identity Cloud admin console.
-
IAM-7248[4]: In IGA sources, the
displayName
andlogo
can now be obtained from the CDN. -
IAM-7874[4]: The Governance > Requests > Settings tab now lets you activate or deactivate Governance LCM.
January 2025
31 Jan 2025
Versions 16460.0, 16466.0
No customer-facing features, enhancements, or fixes released.[1]
29 Jan 2025
Versions 16437.0, 16441.0
No customer-facing features, enhancements, or fixes released.[1]
24 Jan 2025
Versions 16410.0, 16412.0
Enhancements
-
FRAAS-23002: Improvements to OATH support for MFA authenticators
-
Update the default OATH shared secret length from 32 to 40 for existing and new tenants so that tenant administrators can use Google Authenticator with MFA when signing on using their Advanced Identity Cloud native accounts.
-
Make the OATH shared secret length configurable (using a support request) to support other MFA authenticators.
-
23 Jan 2025
Versions 16386.0, 16388.0
No customer-facing features, enhancements, or fixes released.[1]
22 Jan 2025
Versions 16368.0, 16376.0
No customer-facing features, enhancements, or fixes released.[1]
20 Jan 2025
Versions 16345.0, 16348.0
15 Jan 2025
Versions 16294.0, 16297.0
Enhancements
-
FRAAS-23375: You can now obtain the HTTP client location from the
X-Client-City
&X-Client-City-Lat-Long
HTTP headers in Advanced Identity Cloud scripts and journeys.X-Client-City
contains the name of the city from which the request originated, for example,Mountain View
for Mountain View, California. There is no canonical list of valid values for this variable. The city names can contain US-ASCII letters, numbers, spaces, and the following characters:"!#$%&'*+-.^_`|~"
.X-Client-City-Lat-Long
contains the latitude and longitude of the city from which the request originated, for example,37.386051,-122.083851
for a request from Mountain View.
14 Jan 2025
Versions 16276.0, 16278.0
No customer-facing features, enhancements, or fixes released.[1]
10 Jan 2025
Versions 16216.0, 16229.0
Enhancements
-
IAM-6833: Made existing synchronization tokens editable for incremental reconciliations.
-
IAM-7223[4]: Added the ability to set user, role, organization, application, or entitlement objects to provide predefined values for select and multiselect fields in request forms.
03 Jan 2025
Version 15989.0
Enhancements
-
ANALYTICS-459[11]: Report query data is now retained for 30 days for customers using OOTB reports and 90 days for customers with Advanced Reporting[12].
-
ANALYTICS-495[11]: Replace
email
withusername
in User Last Login report. -
ANALYTICS-817[11][3]: Report authors can now query on "Password Last Changed Time" for user entity.
-
ANALYTICS-818[11][3]: Report authors can now query on "Password Expiration Time" for user entity.
Fixes
-
ANALYTICS-474[11]: The User Journey Stats report now provides aggregates by outcome in the report result when more than one outcome is selected.
-
ANALYTICS-837[11]: The User Count by Status report now provides aggregates by status in the report result when more than one outcome is selected
-
ANALYTICS-585[11][3]: Remove Report Admin and Report Owner group selection when creating a new report.
December 2024
17 Dec 2024
Version 16028.0
Enhancements
-
OPENDJ-9287: The password validation mechanism has been enhanced to include checks for portions of attribute values within passwords. This improvement ensures that even partial matches between portions of passwords and portions of attribute values are identified and restricted, thereby enhancing security.
For example, if the password is
abcdef
and the attribute value isabcdef123
, the password is rejected. Similarly, if the password isabcdefAZERTY
and the attribute value isabcdef123
, the password is rejected.
16 Dec 2024
Version 15989.0
This release reintroduces many features, enhancements, and fixes previously present in reverted versions.
Key features
- PingOne Authorize node (TNTP-183)
-
Use this node to send a decision request to a specified decision endpoint in your PingOne Authorize environment.
- PingOne node improvements (SDKS-3468)
-
- PingOne Create, Identify, and Delete Nodes
-
The following PingOne nodes are now available:
- PingOne Identity Match node
-
Use the PingOne Identity Match node to identify if a user exists both in the user repository and in PingOne, using defined attributes.
- PingOne Create User node
-
Create new users in the PingOne platform using the PingOne Create User node. Create users based on an existing user’s properties or choose to create the user anonymously. For example, when used in conjunction with PingOne Verify.
- PingOne Delete User node
-
Delete users from the PingOne platform with the PingOne Delete User node.
- PingOne Verify nodes
-
Use the following PingOne Verify nodes in conjunction with the PingOne Identity Match node, PingOne Create User node, and PingOne Delete User node to create a seamless verification process in your journey:
- PingOne Verify Evaluation node
-
Leverage PingOne Verify to initiate or continue a verification transaction with the PingOne Verify Evaluation Node.
- PingOne Verify Completion Decision node
-
Determine the completion status of the most recent identity verification transaction for an end user.
Use before the PingOne Verify Evaluation node to determine the status of the verification process or after the PingOne Verify Evaluation node using a script to evaluate the transaction.
For example, you can evaluate if the transaction was completed using a passport and route your journey accordingly.
Use these nodes in place of the PingOne Verify Marketplace nodes. - reCAPTCHA Enterprise node (SDKS-3322)
-
The reCAPTCHA Enterprise node node adds Google reCAPTCHA Enterprise support to your journeys.
- SAML application journeys (AME-27850)
-
Added support for SAML application journeys with a new setting on the remote SP. Configure a specific authentication journey that always runs for users authenticating with your SAML 2.0 app, regardless of existing sessions or configured authentication context.
Learn more in Configure a SAML 2.0 application journey.
- Set Failure Details node (AME-27871)
-
Use the Set Failure Details node to configure a localized error message on journey failure. You can also configure extra details in the response body of the failure request.
- Set Success Details node (OPENAM-12335)
-
Use the Set Success Details node to add additional details to the success response of a journey.
- UI support for managing certificates (IAM-5813)
-
You can now use the Advanced Identity Cloud admin console to generate CSRs and upload SSL certificates in your tenant environments.
Learn more in Manage server certificates using the admin console.
Enhancements
-
AME-26050: You can now create Next-generation Policy Condition scripts that have access to all common bindings, such as
openidm
andhttpClient
. Additionally, some existing bindings have been wrapped to improve usability in scripts. -
AME-28228: OAuth 2.0 audit logs now include the OAuth 2.0 client ID and any journey associated with the client.
-
AME-29009: When using the new FIDO Metadata Service, if you link to the FIDO metadata using a URL, Advanced Identity Cloud periodically downloads and updates the latest FIDO metadata based on the
nextUpdate
date specified in the downloaded data. -
AME-29093: Added configuration for integration with WebAuthn Metadata Services (such as the FIDO Metadata Service). This includes a realm-level WebAuthn Metadata service and a new FIDO Certification Level configuration attribute in the WebAuthn Registration Node.
-
FRAAS-22321: You can now obtain the HTTP client location from the
X-Client-Region
HTTP header within your scripts and journeys. TheX-Client-Region
header contains the country (or region) associated with the client’s IP address in the form of a Unicode CLDR region code, such asUS
orFR
. For most countries, these codes correspond directly to ISO-3166-2 codes. -
FRAAS-23073: The SAML scripting adapter now lets scripts access
org.forgerock.http.protocol.*
. -
IAM-3323: You can now use XPath transformation functions with additional Workday application template attributes.
-
IAM-4540: You can now change the border color of a selected input field in journey and end-user pages.
-
IAM-6397: The Advanced Identity Cloud admin console now lets you page through the list of OAuth 2.0 client profiles.
-
OPENAM-23109: During a WebAuthn registration flow, if Store data in transient state is enabled, the Authenticator Attestation Global Unique Identifier (AAGUID) is now added to the node state under the
webauthnData
key.
Fixes
-
AME-28016: When an invalid redirect URI is provided to the
/par
endpoint, the URI mismatch error is nowredirect_uri_mismatch
instead ofinvalid_request
. -
AME-28017: Advanced Identity Cloud now accepts the requested OAuth 2.0 endpoint as a valid JWT audience claim, as per RFC 7519 and RFC 9126.
-
AME-29170: On LDAP Decision node login failure, stack traces are now logged at
debug
level. -
AME-29965: The Configuration Provider node now works with the Inner Tree Evaluator node for nested inner journeys.
-
IAM-1782: Long gateway and agent IDs no longer overflow in the Advanced Identity Cloud admin console.
-
IAM-7523[4]: A user receiving a forwarded fulfillment task now has permission to approve or reject the task.
-
IAM-7537[4]: Governance functionality is now only shown for the
alpha
realm. -
IAM-7689[4]: The Advanced Identity Cloud admin console now displays the Assigned To value in the task list for a user assigned to a role who receives a forwarded fulfillment task.
-
OPENAM-18252: Journeys acting on multiple identities now successfully update
universalId
in the journey context during the authentication flow. -
OPENAM-20314: Added the ability to indicate whether an OIDC provider doesn’t return a unique value for the
sub
claim. -
OPENAM-22966: Social IDPs now support NONE as a client authentication method. This option should be used if the provider doesn’t require client authentication at the token endpoint.
03 Dec 2024
02 Dec 2024
Version 15824.0
This version has been reverted and all associated changes withdrawn. |
This release reintroduces many features, enhancements, and fixes previously present in reverted versions.
Key features
- PingOne Authorize node
-
Use this node to send a decision request to a specified decision endpoint in your PingOne Authorize environment.
- PingOne Create, Identify, and Delete Nodes
-
The following PingOne nodes are now available:
- PingOne Identity Match node
-
Use the PingOne Identity Match node to identify if a user exists both in the user repository and in PingOne, using defined attributes.
- PingOne Create User node
-
Create new users in the PingOne platform using the PingOne Create User node. Create users based off of an existing user’s properties or choose to create the user anonymously. For example, when used in conjunction with PingOne Verify.
- PingOne Delete User node
-
Delete users from the PingOne platform with the PingOne Delete User node.
- PingOne Verify Nodes
-
Use the following PingOne Verify nodes in conjunction with the PingOne Identity Match node, PingOne Create User node, and PingOne Delete User node to create a seamless verification process in your journey:
- PingOne Verify Evaluation node
-
Leverage PingOne Verify to initiate or continue a verification transaction with the PingOne Verify Evaluation Node.
- PingOne Verify Completion Decision node
-
Determine the completion status of the most recent identity verification transaction for an end user.
Use before the PingOne Verify Evaluation node to determine the status of the verification process or after the PingOne Verify Evaluation node using a script to evaluate the transaction.
For example, you can evaluate if the transaction was completed using a passport and route your journey accordingly.
Use these nodes in place of the PingOne Verify Marketplace nodes. - reCAPTCHA Enterprise node
-
The reCAPTCHA Enterprise node node adds Google reCAPTCHA Enterprise support to your journeys.
- SAML application journeys (AME-27850)
-
Added support for SAML application journeys with a new setting on the remote SP. Configure a specific authentication journey that always runs for users authenticating with your SAML 2.0 app, regardless of existing sessions or configured authentication context.
Learn more in Configure a SAML 2.0 application journey.
- Set Failure Details node (AME-27871)
-
Use the Set Failure Details node to configure a localized error message on journey failure. You can also configure extra details in the response body of the failure request.
- Set Success Details node (OPENAM-12335)
-
Use the Set Success Details node to add additional details to the success response of a journey.
Enhancements
-
AME-26050: You can now create Next-generation Policy Condition scripts that have access to all common bindings, such as
openidm
andhttpClient
. Additionally, some existing bindings have been wrapped to improve usability in scripts. -
AME-28228: OAuth 2.0 audit logs now include the OAuth 2.0 client ID and any journey associated with the client.
-
AME-29009: When using the new FIDO Metadata Service, if you link to the FIDO metadata using a URL, Advanced Identity Cloud periodically downloads and updates the latest FIDO metadata based on the
nextUpdate
date specified in the downloaded data. -
AME-29093: Added configuration for integration with WebAuthn Metadata Services (such as the FIDO Metadata Service). This includes a realm-level WebAuthn Metadata service and a new FIDO Certification Level configuration attribute in the WebAuthn Registration Node.
-
AME-29769: The Social Provider Handler node has a new configuration option, Store Tokens, that allows access and refresh tokens to be stored in the transient state.
-
FRAAS-22321: You can now obtain the HTTP client location from the
X-Client-Region
HTTP header within your scripts and journeys. TheX-Client-Region
header contains the country (or region) associated with the client’s IP address in the form of a Unicode CLDR region code, such asUS
orFR
. For most countries, these codes correspond directly to ISO-3166-2 codes. -
IAM-3323: You can now use XPath transformation functions with additional Workday application template attributes.
-
IAM-4540: You can now change the border color of a selected input field in journey and end-user pages.
-
OPENAM-23109: During a WebAuthn registration flow, if Store data in transient state is enabled, the Authenticator Attestation Global Unique Identifier (AAGUID) is now added to the node state under the
webauthnData
key.
Fixes
-
AME-28016: When an invalid redirect URI is provided to the
/par
endpoint, the URI mismatch error is nowredirect_uri_mismatch
instead ofinvalid_request
. -
AME-28017: Advanced Identity Cloud now accepts the requested OAuth 2.0 endpoint as a valid JWT audience claim, as per RFC 7519 and RFC 9126.
-
AME-28906: The stack trace of an authentication exception generated on login failure is now logged only when
debug
level logging is enabled. -
AME-29170: On LDAP Decision node login failure, stack traces are now logged at
debug
level. -
IAM-7523[4]: A user receiving a forwarded fulfillment task now has permission to approve or reject the task.
-
IAM-7537[4]: Governance functionality is now only shown for the
alpha
realm. -
OPENAM-18252: Journeys acting on multiple identities now successfully update
universalId
in the journey context during the authentication flow. -
OPENAM-20314: Added the ability to indicate whether an OIDC provider doesn’t return a unique value for the
sub
claim. -
OPENAM-22966: Social IDPs now support
NONE
as a client authentication method. Use this option if the provider doesn’t require client authentication at the token endpoint.