USAS-R Releases
...
- The account change process has been corrected to properly handle overpaid purchase orders. Previously the amounts moved to new accounts related to an overpaid PO was resulting in negative remaining encumbrances. This change impacted two specific districts and also includes a patch to correct the encumbrances for those districts' transactions.
- Prevent password from being audited in the Password Change event
A bug was discovered in the 8.46.0 release of USAS-R that could allow the writing of a local user's password to a database table as plaintext. This could only happen if the user's password was reset, either by the admin user or from the change password option on the home page, and the password change happened between the release of 8.46.0 (5/6/2022) and 8.46.1 (5/10/2022). The password could be included in an Auditable Events template report that is only accessible by users with the ADMIN_AUDITEVENTS permissions. By default, this includes the Admin user and anyone with the SYSMAN_USER role in USAS-R.
The hotfix will remove any of the possible stored passwords from the Auditable Events table and also prevent the password property from being audited in the future.
To see if any users have changed their passwords since USAS-R 8.46.0, run the SSDT Auditable Events report with the start date of 5/6/2022 and end date of 5/10/2022. Once the report generates look for User Password Change Event and Admin Password Change Event. It is recommended that any user you find here should have its password reset.
Improvements
- Password changes and change attempts are now logged in audit log. This includes changes an individual does for themself or themselves or a user with proper permissions does for another user's account.
...
- 1099 PDF documents were created for both the 1099-MISC and 1099-NEC options. The new PDF copies that are available with this release can be found when selecting the new Output File Type value "Reference Copy" . This option will display a new "1099 Copy" field. The available PDF documents are Copy B, Copy C, Copy 1 & Copy 2. Copy A will be completed under a later Jira issue. This is not the folder/sealer copy that will be provided to the vendor. Additional 1099 printing issues are being worked and when 1099 printing from USAS-R is fully available we will detail that in the release notes. The PDF versions used last year are still available under the Output File Type: PDF Format.
Patches
- A patch to clean up bad data migrated from Classic. This patch is specific to a single district that migrated in 2019, prior to the ability to post encumbrance impacts.
...
W2 City Overrides - Always display help screen variables when in edit mode
New Features
Handle 'Withholding Based on Earnings' STRS Advance
...
- Implemented an environment variable to assist with resetting the password on the admin user account if it has been forgotten. The variable name is applicationAdminReset and it should be set to TRUE in the ssdt-inventory-app.properties file. It does not matter where in the properties file you include this new variable. An example is available in the Inventory Installation and Migration Guide. The application container must be recreated after this property is set to true by using the /ssdt/prod/update-inventory-app.sh script. If this property is defined in the ssdt-inventory-app.properties file and the script is run, the admin user account password will be reset to the value defined in the "adminPassword" variable defined in the ssdt-inventory-shared.properties file. Please note, recreating the container will cause the application to be unresponsive and no one will be able to access the application until the container is fully started.
- Note: Any time the application is restarted the following values on the admin user account will be cleared: Account Expiration, Locked, Enabled, External Authentication. This is to prevent rendering the admin account unusable.
- Note: If you need the admin account "unlocked" or "enabled", that is a different solution. The application simply needs to be restarted in these cases, The admin account can become locked if the current system date is later than the expiration date on the user account. The admin account can become disabled via the flag on the user account.