What's new
New Identity Flows versions are released and announced on a varying cadence. Occasionally, new versions that include only performance, stability and bug fixes, and do not require customer actions, are released without an announcement.
Version 23-8.1
What's new in this release?
Mutual TLS (mTLS) is a secure method for mutual authentication, ensuring both ends of a network connection are legitimate by verifying their respective private keys. This verification is reinforced by the information within their TLS certificates. mTLS plays a critical role in Zero Trust security frameworks, verifying users, devices, and servers within an organization, thereby enhancing overall security, including the protection of APIs.
To facilitate this functionality, we've introduced a new section in the Authorization settings called Client certification . You can add the required client certificates and keys in this section. With these credentials in place, Identity Flows can present the client certificates during each call to any server supporting mTLS authetication, enabling a secure and trusted communication channel without any compromise on data integrity.
The Identity Flows Admin now has the ability to delegate two new roles to users, based on business needs. The details of these new roles are as follows:
Flows Contributor -
As a flows contributor, you have various abilities. These include the ability to create, read, write, and run your own flows, as well as delete them as needed. In terms of connectors, you can utilize those created by others, while also having editing rights for the ones you've created. However, you cannot delete connectors.
You can manage authorizations that you've established, allowing you to view, edit, or delete them. Moreover, all forms are visible to you, but your editing and deletion rights apply solely to the ones you've created. In the realm of notifications, only those pertaining to you are viewable.
Lastly, you have full rights over datastores, enabling you to create, view, edit, and delete them as per your requirements.
Flows Read - The Flows Read role is a view-only role. Users with this role can view builder OIDC Integration, flows, forms, connectors, notifications, authorizations, and domain information. Additionally, they have the ability to export all flows.
A user must be assigned a Identity Flows role in order to access the Identity Flows portal.
Bug fixes
Area |
Description |
---|---|
My connectors |
Fixed an issue where imported connectors were not showing in the My connectors list when the flow is exported from other tenants. |
Stop node |
Fixed an issue in the Stop node where users were unable to select Custom Response Templates inside body parameters, under Enable custom response. |
Import flow |
Fixed an issue where the logo was not marked as required when importing a flow. |
Forms |
Fixed an issue where the form displays mandatory field errors upon loading, rather than waiting for user interaction with the fields. |
OpenID Connect URL |
Fixed an issue where the OpenID Connect URL was redirecting to the builder URL when the flow name has brackets. |
Branch and split conditions |
Fixed an issue where branch and split nodes weren't working if the branch was under a split node. |
Loop condition |
Fixed an issue where loop break was not working as expected. |
Import connector |
Fixed an issue with importing Twilio OpenAPI. |
Known issues
Issue |
Workaround |
---|---|
In the flow notification section, all fields of a form may not be shown while debugging from the notification logs. |
To view the objects in the notification section, map the missing form fields to a datastore object. |