On Wednesday, August 5, 2026 the IAMIAM Identity and Access Management (IAM) is a set of policies, processes, and technologies designed to ensure that the right individuals (identities) have the right access to resources within an organization. IAM involves managing and securing digital identities, controlling access to systems and data, and maintaining the confidentiality, integrity, and availability of information. Team released version 2026.2.5 of midPoint, implementing the following changes:
- Added AWS Lambda to copy UT System files from the Production SFTP server to the Test and Qual folder.
- Created a custom resource that ensures successful deletion of the APIAPI An Application Programming Interface (API) is a set of routines, protocols, and tools for building software applications. Certificate to address an error that could arise when resetting midPoint during maintenance.
- Updated TEDTED The uTexas Enterprise Directory (TED) is the University’s enterprise directory. See uTexas Enterprise Directory (TED) in the service catalog for more information. and ADAD Active Directory (AD) is a directory service from Microsoft which implements Internet standard directory and naming protocols. See Austin Active Directory (Austin AD) in the service catalog for the University’s local implementation. correlations of the name attribute.
- Change the AWS lambda configuration to backup the Workday full and delta files in the production envirnment only.
- Modify the AWS lambda in midPoint non-production environments so that the Workday full and delta files are deleted without a backup.
- The Email attribute and value will not be sent to TIMTIM The uTexas Identity Manager (TIM) is the University’s identity manager. See uTexas Identity Manager (TIM) in the service catalog for more information. when the value is blank.
- A caching issue causing 403 errors in TIM when multiple System of Record requests are sent to midPoint has been resolved.
- The manager attribute in the Workday People schema and the Global User Template is now multi-valued.
- Updated the key name on the AWS lambda function for the Workday SupOrg file.
- The schedule for the AWS lambda UT System file removal on the SFTP server has been modified to occur daily at midnight.
- Added Splunk logging for when:
- Workday full file, Workday delta files, and Workday SupOrg files are on the SFTP server.
- Workday full file and Workday delta files are backed up.
- Workday full file, Workday delta files, and Worday SupOrg files are processed.
- Workday full file, Workday delta files, and Workday SupOrg files are deleted off the SFTP server.
- UT System files are on the SFTP server.
- UT System files are copied from the production SFTP server to the Test and Qual environments.
- UT System files are combined and processed.
- UT System files are deleted from the SFTP server.
- New automated alert notifictions when:
- Workday full file, Workday delta files, or Workday SupOrg files are not received on the SFTP server.
- Workday full file, Workday delta files, or Workday SupOrg files on the SFTP server are greater than 24 hours old.
- UT System files are not recieved on the SFTP server.
- UT System files on the SFTP server are greater than 24 hours old.
- Additional internal debugging alerts.
- Post-release: Consolidate the AWS S3 buckets for backed-up Workday full and delta files into a single bucket.
