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.
May 2025
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[3]: Added support for using custom identity objects in the 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[3]: 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 custom 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: Prevented jobs being scheduled with frequencies that caused 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 Platform UI Login application.
-
IAM-8361: Fixed the Save button in the Edit Bookmark application to be 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[2]: 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)[2][4]
-
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 in Advanced Reporting.
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[2]: In the analytics report editor in Advanced Reporting, you can now reorder columns by dragging and dropping them.
-
IAM-7841/ANALYTICS-840[2]: 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[3]: 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[3]: 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[3]: In IGA sources, the
displayName
andlogo
can now be obtained from the CDN. -
IAM-7874[3]: 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[3]: 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[5]: Report query data is now retained for 30 days for customers using OOTB reports and 90 days for customers with Advanced Reporting[6].
-
ANALYTICS-495[5]: Replace
email
withusername
in User Last Login report. -
ANALYTICS-817[5][2]: Report authors can now query on "Password Last Changed Time" for user entity.
-
ANALYTICS-818[5][2]: Report authors can now query on "Password Expiration Time" for user entity.
Fixes
-
ANALYTICS-474[5]: The User Journey Stats report now provides aggregates by outcome in the report result when more than one outcome is selected.
-
ANALYTICS-837[5]: The User Count by Status report now provides aggregates by status in the report result when more than one outcome is selected
-
ANALYTICS-585[5][2]: 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 SSL 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[3]: A user receiving a forwarded fulfillment task now has permission to approve or reject the task.
-
IAM-7537[3]: Governance functionality is now only shown for the
alpha
realm. -
IAM-7689[3]: 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 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[3]: A user receiving a forwarded fulfillment task now has permission to approve or reject the task.
-
IAM-7537[3]: 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.