The latest hotfix release (9.2.0-9) is comprehensive and resolves all issues addressed by the hotfixes in this table:
Adaptive Authentication Redirection – Redirecting the user via an Adaptive Authentication policy with a static query string parameter resulted in a query string with an invalid format.
User Risk Analysis Response – When retrieving a user risk score from certain third-party providers, SecureAuth IdP was not reading a valid score due to a null reference.
Windows SSO Enhancement – Some IIS settings necessary for Windows SSO / authentication must be manually entered in the web.config, but SecureAuth IdP would remove all these settings if a change was subsequently made on the Workflow tab.
The latest hotfix release (9.1.0-42) is comprehensive and resolves all issues addressed by the hotfixes in this table:
OIDC EndSession Redirect – Redirect and session end was not occurring due to the 'post_logout_redirect_uri' parameter requiring the presence of the 'id_token_hint' parameter. Redirect now functions with the presence of 'client_id' only, and does not require 'id_token_hint'.
Create User Failure for eDirectory – Create User page integrated with eDirectory was not functioning due to hardcoded attribute information.
NOTE: This fix enables the creation of users, but certain functionalities of the page are not supported for eDirectory at this time.
Proxy Settings for OIDC Encryption Key Retrieval – Proxy settings configured in SecureAuth IdP are not applied when retrieving OIDC encryption keys.
Create User Group Designation SQL – Create User page with SQL data store integration does not associate users to groups on the page during creation.
NOTE: This fix requires a new stored procedure provided by SecureAuth Support (see contact information below).
Novell eDirectory Lookup – During login, a user’s profile was not accessed successfully and the self-service password reset was unsupported.
Mobile QR Code Enrollment – When device limitation is enforced, false errors would occur during QR code enrollment.
SA Cloud Timeout and Fail Open – Due to extended timeouts and no fail open functionality, users were unable to log in when SA Cloud services are down.
Errant Calls to Invalid URLs – Calls made for IP Evaluation were hitting the wrong endpoint URLs.
Bad IPv6 Handling – During Adaptive Authentication analysis, IPv6 calls created issues with the evaluation.
9.1.0-39 or earlier
JWT Missing Claim – In OAuth 2.0 Client Credential Flow, the ‘sub’ (subject) claim was missing in the JWT.
Encryption Functionality – Encryption functionality was static due to the disability of this feature.
OTPValidateThrottle PUT Call – OTPValidateThrottle PUT call was resetting the count for both values (Select vs. Validate counts).
Self-service PIN Update – The Update button needed two clicks to save new PIN information.
RADIUS Server Timeouts – RADIUS Server requests were timing out when under a high load.
Slow Response – When connected to a Syslog Server, too many UDP clients created a massive slow down.
Tivoli Directory Device Recognition – Device / Browser Profiles were not accurately saved to Tivoli user profiles.
Link-to-Accept with Proxy – Link-to-Accept did not properly go through the configured proxy settings (both SMS and email).
Device Recognition on IE10 – PixelRatio property analyzed for fingerprinting was unsupported in IE10 and therefore returned a null response and invalid browser profile.
YubiKey Validation Call Failure – API calls to validate the YubiKey login fail due to character limitations in the string.
Account Management Error – Updating the OATH Seed on the Account Management page created an error due to split directory integrations for membership and profile.
SMTP Timeout Errors – Using the Authentication API to request OTP emails, the user experienced SMTP timeout errors.
HID Token Read Failure – Login process was unable to read the OATH Seed from an HID token for MFA, and SecureAuth IdP was unable to read the OATH Seed from HID token for post-authentication.
2016 Light Theme Login Page – When pasting a password (from password manager, for example), the Submit button did not change color and the mouse cursor showed the ‘no entry’ icon. Clicking the button worked, but visually appeared as though it would not.
Verbiage Customizations – When a user’s browser is not set to English and the preferred language is not selected in the SecureAuth IdP configuration, then the browser defaulted to English, but without the verbiage customizations made in the Web Admin.
Invalid Username not Updating – With workflow type set to Username & Password, when the user entered an invalid username and then corrected it, the username was still considered invalid and the page reverted the text back to the original invalid entry.
OTPValidate Throttle not Counting – Instead of creating a unique counter for OTPValidate, the MultiFactorIntervalThrottle counter was used instead.
Login for Windows UI – Various UI defects were resolved in Login for Windows.
Username Overflow – On the Account Management page, the username overflowed into the next text box.
OIDC Redirect URI with Localhost – For OIDC integrations, the Redirect URI did not support localhost.
NumberProfile API Server Error – Requests to the phone number analysis endpoint with an invalid number (e.g. 123456789) generated a server error response.
Password Requirements for Create User Page – Password requirements configured on the Web Admin were not applied to the Create User page.
Unwanted Verbiage on Page – A flag on a page displayed unwanted verbiage on client-side pages.
Duplicate Knowledge Based Questions – Users were able to select the same KBQ multiple times, thus only having one question to answer for Multi-Factor Authentication.
No Automatic Redirect – Users were not automatically redirected from SecureAuth IdP with an OIDC token to the relaying application.
Invalid User Error – LDAP users attempting to log in continually received an “Invalid User” error.
OATH Token Invalidation – After upgrading to version 9.1, existing OATH Tokens were no longer valid and required re-provisioning.
Login for Windows Configuration – Configuration settings for new Login for Windows product were not available in the Web Admin.
FIPS Compliance – SecureAuth IdP updates were made for FIPS Compliance requirements.
Admin API HMAC Authentication – It was possible to remove HMAC authentication from the Admin API.
Authentication API Throttling – The Multi-Factor Throttling count doubled based on selection and validation of the OTP, thereby rendering the configuration inaccurate.
Web.config URL Update – Values for some URLs were incorrect in the web.config.
Compilation Error – The SISU code file contained a compilation error.
ChangePassword Error – Username was missing a domain slash for Change Password via the API.
Link-to-Accept UI Update – Color of the button was incorrect.
Authentication API OATH Token Failure – OATH Token was not working as a viable Multi-Factor Authentication option via the Authentication API.
Description: This hotfix makes the appliance more secure, strengthening the integration with the Credential Provider, by validating the username, password, and Time-based Passcode (TOTP) via Integrated Windows Authentication (IWA) and SecureAuth Cloud Services.
Description: This hotfix resolves a potential security vulnerability for credentials used in the Web Services (Multi-Data Store) configured on the Membership Connection Settings section of the Data tab and on the FBA WebService section of the Workflow tab. If the SecureAuth IdP administrator has not changed the default password after initial configuration of the SecureAuth idP appliance, then the appliance may be vulnerable.
Description: This hotfix resolves an issue in which certain SAML conditions are not being calculated properly in SecureAuth IdP, and also resolves handling subsequent SAML assertions signed as SHA-256.
Description: This hotfix resolves issues related to the 2016 Theme, and should be applied to IdP appliances running version 8.2. If you are not affected by issues this hotfix addresses (see documentation for details), it is recommended you install SecureAuth IdP version 9.0 or greater.
Description: This hotfix resolves the issue for SecureAuth IdP appliances running 8.1 that are not generating logs to the Event Viewer. Windows Event Viewer is used by the system administrator to view events for all programs on a machine to monitor its performance, identify and troubleshoot issues, etc.
Description: This hotfix resolves an issue in which unauthorized users could gain administrative access in some configuration scenarios. It is recommended you install this hotfix on all appliances running versions 6.0 through 8.0.3. Rename the file with a .exe extension after downloading the file.
Description: This hotfix resolves an issue for configuration scenarios that give authenticated users access to content that should be restricted only to authorized users. SecureAuth recommends applying this hotfix on all SecureAuth IdP appliances running versions 6.0 through 8.0.1. Rename the file with a .exe extension after downloading.
Description: This hotfix resolves three known issues in the 8.0 release and should be applied to SecureAuth IdP 8.0 builds on Windows 2012 R2 shipped before September 24, 2014. Issues resolved in this hotfix: 1. Authentication Error Message: Error messages appear because the IdP application directory in IIS and its corresponding IdP physical path have not been created in the appliance 2. Deleted Realm Error: The error is a result of a bug in the rc.js and rc.min.js files found in the D:\SecureAuth\SecureAuth0\Scripts folder. 3. User name / Password Error message: The error is a result of a bug in the secureauth.foundation.dll file.
Description: This hotfix resolves an issue for SecureAuth IdP version 7.5 in which the SecureAuth.IdentityModel.WSFederation.dll can cause errors in WS-Federation workflows. This hotfix updates the DLL to restore proper operation of the WS-Federation capability. This issue, resolved in SecureAuth 7.5.1, only impacts 7.5.
Description: This hotfix resolves the issue for SecureAuth IdP versions prior to 7.5 in which users receive a .NET error during the pre-authentication portion of the workflow in environments using an ASPNETDB datastore with device fingerprinting.