This release of Secure Work includes three important bug fixes to enhance stability and performance.
What's New
-
New API: Retrieve Credential Binding Jobs
We’ve added support for retrieving credential binding jobs through a new API resource.
Endpoint:
GET /v2/binding-jobs/{binding_job_id}Details:
Use this endpoint to check the status and details of an existing binding job.
If the delivery method for the job is
SHORT_CODE, the response will not include the short code. (Short codes are only available at the time of creating a binding job.)This enhancement makes it easier to track the lifecycle of binding jobs.
View API Documentation
Bug Fixes
-
Integration Password Entry
Fixed an issue in the Secure Work admin console where entering a password during integration configuration incorrectly triggered a 'Credentials not valid' error. Additionally, sensitive fields (such as passwords and API tokens) now support both manual entry and copy/paste functionality for improved user experience. -
Endpoint URL Validation
Improved endpoint configuration by preventing users from entering URLs with trailing slashes. -
Event Log Noise Reduction
Removed unnecessary 'User Authentication – UNAUTHORIZED' events that contained no meaningful details, reducing noise in admin event logs.
Comments
0 comments
Article is closed for comments.