Enhancement Release 13.2.0 – AODA & Multi Factor Authentication (MFA)
13.2.0 Go Live: November 5th, 2025
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
SD-69067
| MFA-Backend Development | This change is in a disabled state currently Developed backend functionality to enforce two-factor authentication across user accounts, providing secure token validation, account setup flows, and integration with existing authentication | Staff Profile- Security |
SD-70375 | MFA- Prompt Users to Register for MFA During Login- APEXA Staff | This change is in a disabled state currently Developed frontend functionality to enforce two-factor authentication registration for APEXA staff users | Staff Profile- Security |
SD-70544 | MFA- Enforce TOTP Prompt on all Subsequent User Logins-APEXA Staff | This change is in a disabled state currently Developed frontend functionality to enforce two-factor authentication verification for APEXA staff users before accessing the system on subsequent logins. | Staff Profile- Security |
SD-73339 | MFA- Restore Inclusion Functionality | A configuration issue prevented users from being added to the inclusion list to prompt MFA registration. Users will now be correctly enrolled and prompted for MFA if added to the inclusion list | Staff Profile- Security |
SD-73288 | MFA- Improved Error Handling for Subsequent Logins | Technical failures during subsequent MFA logins were not displaying error messages to users, these are now being displayed | Bug Fix- Staff Profile- Security |
SD-73217 | MFA- Deleted Staff Accounts Prompted For TOTP | Deleted staff profiles were being prompted to enter a TOTP during login. Deleted accounts are now correctly recognized and not triggered for MFA verification | Bug Fix- Staff Profile- Security |
SD-73246 | MFA- Update Text in Registration Email | Some text in the MFA registration email was duplicated; the duplicated text has now been removed | Staff Profile- Security |
SD-72819
| Support- Resolve Performance Issues in In Trust | Searches for contractor and contract records in In Trust were timing out, we extended the timeout duration in In Trust to improve performance | In Trust- Performance |
SD-73109
| Support-Resolve Performance Issue for Package Revisions | Ineligible contracts were not displayed in the Ineligible tab after a package revision; we extended the timeout duration to improve performance | Package Revisions- Performance |
SD-72151
| AODA - Advisor Contract Request - New Request | 2 instances of guideline 1.1.1 were resolved · Non-text Content o Contract Requests - New Request screen - Radio button's sub text · I want to request a contract with a new company · I want to request a contract with a new MGA/AGA · I already have an AGA/MGA contract, I need a new Carrier contract · I want to request a new Carrier-Direct contract · I need to transfer one of my Carrier Contracts o Contract request - "What would you like to do" screen - Hidden area focuses · Above Request a new contract or transfer · View my previous contract requests | Regulatory -AODA |
SD-71857
| AODA - Client Profile - Dashboard | 1 instance of guideline 2.4.4 was resolved · Link Purpose (In Context)
3 instances of guideline 2.4.7 were resolved · Focus Visible
4 instances of guideline 4.1.2 were resolved · Name, Role, Value | Regulatory -AODA |
SD-72176
| AODA - Advisor Contract Request- Request a Contract with New MGA/AGA | 1 instance of guideline 1.1.1 was resolved · Non-text Content o Request a contract with a new MGA/AGA" screen - Radio button's sub text § I want to request a contract directly with the MGA/AGA § I want to go through another corporation to contract with the MGA/AGA | Regulatory -AODA |
SD-72180 | AODA - Advisor - Contract Search
| 1 instance of guideline 3.3.2 was resolved Labels or Instructions "Contract Search" screen - Search Input Field | Regulatory -AODA |
SD-72527
| AODA- Incorrect Focus Order | Focus order in the “Banking Information” screen was misaligned, this has now displayed properly | Bug Fix-Regulatory -AODA |
SD-72824: | AODA- Advisor Profile- Correct Position of Delete Buttons | The location of “Delete” buttons on Advisor profiles was misplaced; the “Delete” buttons have now been correctly positioned | Bug-Fix- Regulatory -AODA |
SD-72534
| AODA- Client Profile-Licenses-Banner Messages Partially Read by Screen Reader | Banner Message in the Licence Section was not being fully read by screen readers; this is now correctly identified by screen readers | Bug-Fix- Regulatory -AODA |
SD-73142 | Technical Item - Set Specific IIS Application Pool Recycle Schedule for All PRD Web Servers | To improve memory management and reduce unexpected performance drops, we configured a specific recycling schedule for IIS application pools across all production web servers
| Technical -Internal |
SD-72761 | Technical Item - Database - Evaluate and Execute Index Maintenance Post Table Cleanup | To optimize storage and performance, we implemented a mechanism to section and execute index maintenance to clean up redundant data in PRD
| Technical -Internal |
Guideline List -Affected Guidelines
Description |
|---|
1.1.1 - Non-text Content - Level A - All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. |
2.4.4 - Link Purpose (In Context) - The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. |
2.4.7 Focus Visible - Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. |
3.3.2 Labels or Instructions - Labels or instructions are provided when content requires user input. |
4.1.2 - Name, Role, Value - For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. |