Production release of Okta Workflows 2024.07.2 began deployment on August 6, 2024.
Okta Privileged Access connector now available
The Okta Privileged Access connector is now available in Okta Workflows with the following cards:
- Create Access Report
- Create Project
- Create Project Enrollment Token
- Create Resource Group
- Custom API Action
- Delete Project
- Delete Resource Group
- Delete Server
- Download Access Report
- Find Group By Name
- Find Groups
- Find Project By Name
- Find Resource Group By Name
- Find Servers
- Find Service User By Username
- Find Users
- List Access Reports
- List Enrolled Servers in Project
- List Project Enrollment Tokens
- List Resource Group Projects
- List Resource Groups
- List Service Accounts
- Retrieve Access Report
- Update Resource Group
See Okta Privileged Access connector.
Fixes in Okta Workflows
- OKTA-619031When a table column with a True/False field type had a default value of True, the properties dialog for the column incorrectly displayed the default value as False.
- OKTA-653941The text size on the Flow Activation button made it difficult to read.
- OKTA-736923The Multipart Upload function card didn’t pass the HTTP content-type header for a file upload.
- OKTA-742519For the AWS S3 connector, the Read Object Tags card returned an invalid input type error instead of a list of tags set for the specified object.
- OKTA-744174For the AWS S3 connector, the Upload Object card didn’t pass through the Object Lock Retain Until Date field when uploading an object.
- OKTA-747044In the Execution Log Streaming EA feature, setting a custom body event sometimes caused the downstream system to return an invalid request error.
- OKTA-748261Redirect URL values entered for the OAuth 2.0 Auth Code flow in Connector Builder were incorrectly appended with a :443 port.
- OKTA-750773In the Workflows Console, the documentation links for the Execution Log Streaming and Execution History Inspector EA features pointed to incorrect destination URLs.
- OKTA-752756On the Flow Chart page, parts of the flow navigation were hidden or difficult to read if the browser window was small, if the flow was very large, or if the flow contained a card with nested or branched areas (like If/ElseIf).