Zero Trust API - Release Notes
- What’s New in Superna Zero Trust API Release 2.5.8.1 - Coming Soon!
- Supported OneFS releases
- Feature Support Matrix
- End of Life Notifications
- Deprecation Notices
- Release Notes
- New in 2.5.8.1 - Coming Soon!
- T22349 Zero Trust API critical path snapshot rate limits and expiry
- Known Issues
- T22985 Zero Trust API cannot lockout an account with the # in the name
- Known Limitations
- T22990 Zero Trust API cannot lockout ECS user
- T22989 Zero Trust API cannot lockout NFS user
What’s New in Superna Zero Trust API Release 2.5.8.1 - Coming Soon!
What’s New! In Superna Zero Trust API can be found here.
Supported OneFS releases
See Current Release - Release Notes Ransomware Defender
Feature Support Matrix
End of Life Notifications
NA
End of Life Notifications for all products are available here.Deprecation Notices
Release Notes
New in 2.5.8.1 - Coming Soon!
T22349 Zero Trust API critical path snapshot rate limits and expiry
Critical path snapshot initiated by the Zero Trust API using POST /v2/ransomware/criticalpaths will not take another snapshot if a previous snapshot exists that has been taken in the previous configured dead time which is 1 hour by default. Also critical path snapshot created by the API have a 4 hour expiry by default.
Known Issues
T22985 Zero Trust API cannot lockout an account with the # in the name
An account name with a # in the name does not get locked out when using the Zero Trust API /v2/ransomware/lockout API. A 404 not found response is returned.
Workaround: Use manual steps to block access to the account.
Known Limitations
T22990 Zero Trust API cannot lockout ECS user
The Zero Trust API cannot be used to issue a lockout for an ECS user.
—————————————————–
T22989 Zero Trust API cannot lockout NFS user
The Zero Trust API cannot be used to issue a lockout for an NFS export.