VALT 6.7.4-1: Difference between revisions
Jump to navigation
Jump to search
IVSWikiBlue (talk | contribs) No edit summary |
IVSWikiBlue (talk | contribs) No edit summary |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
September | September 22nd, 2026 | ||
'''Application''' | '''Application''' | ||
* Fixed issue where users who have never previously changed their passwords could not perform API authentication if password complexity is enabled | * Fixed issue where users who have never previously changed their passwords could not perform API authentication if password complexity is enabled | ||
* Fixed issue in Schedules where one failed recurring schedule instance would cause all of that schedule's following scheduled instances to fail | * Fixed issue in Schedules where one failed recurring schedule instance would cause all of that schedule's following scheduled instances to fail | ||
* Fixed issue in Admin > Containers that allowed users to create a new container without a specified parent container | |||
* Record Retention Rules | |||
** Added a time field to the "Keep Until" retention rule | |||
** Fixed issue where records would delete a day after the selected "Keep Until" date | |||
* User group management & SSO | * User group management & SSO | ||
** Fixed issue with SSO User Mapping rules so the lowest rule in the list takes precedence instead of the top | ** Fixed issue with SSO User Mapping rules so the lowest rule in the list takes precedence instead of the top | ||
** When a user clicks the delete button for a user group associated with a SSO User Mapping rule, they now receive an informed warning that the associated rule will also be deleted | ** When a user clicks the delete button for a user group associated with a SSO User Mapping rule, they now receive an informed warning that the associated rule will also be deleted | ||
** When a user group associated with a SSO User Mapping rule is deleted, the associated rule is also deleted | ** When a user group associated with a SSO User Mapping rule is deleted, the associated rule is also deleted | ||
* | |||
** | '''Technical''' | ||
** | * Updated packages and frameworks | ||
** Web Docker Image: OS Alpine Linux 3.23.6 | |||
** Nginx Reverse Proxy Docker Image: Nginx 1.30.5-1 | |||
** Redis Docker Image: Redis 8.6.7 | |||
Latest revision as of 15:44, 22 September 2026
September 22nd, 2026
Application
- Fixed issue where users who have never previously changed their passwords could not perform API authentication if password complexity is enabled
- Fixed issue in Schedules where one failed recurring schedule instance would cause all of that schedule's following scheduled instances to fail
- Fixed issue in Admin > Containers that allowed users to create a new container without a specified parent container
- Record Retention Rules
- Added a time field to the "Keep Until" retention rule
- Fixed issue where records would delete a day after the selected "Keep Until" date
- User group management & SSO
- Fixed issue with SSO User Mapping rules so the lowest rule in the list takes precedence instead of the top
- When a user clicks the delete button for a user group associated with a SSO User Mapping rule, they now receive an informed warning that the associated rule will also be deleted
- When a user group associated with a SSO User Mapping rule is deleted, the associated rule is also deleted
Technical
- Updated packages and frameworks
- Web Docker Image: OS Alpine Linux 3.23.6
- Nginx Reverse Proxy Docker Image: Nginx 1.30.5-1
- Redis Docker Image: Redis 8.6.7