244141 – Due to enhanced security changes within Starling Two-Factor Authentication, Password Manager 5.8.2 Starling Two-Factor Authentication unjoin function fails when the TLS 1.2 protocol is enforced. Additionally, in Password Manager 5.8.2 the activity Authenticate with Starling Two-Factor Authentication SMS and Phone Call options also fail if Password Manager is already joined to Starling Two-Factor Authentication.
This cumulative hotfix also contains all previously discovered issues since the release of Password Manager 5.8. For a full listing of resolved issues please consult the included documentation within the hotfix package.
Starling Two-Factor Authentication has been enhanced to only accept the TLS 1.2 protocol.
244141, 236819, 236820, 217557, 106778, 100051, 100266, 101164, 108986, 109946, 108086, 110869, 111445, 126565, 125661, 127765, 170379, 184323, 201031, 220312, 108355/122791, 112471, 114913, 115815, 142180, 169932, 167521, 216728, 218133, 218760, 220083, 221967, 223773, 222330, 235732, 233548, 122971, 110595, 141501
NOTE: During the hotfix installation, click NO when prompted for a system restart. Perform a manual restart after the installation of the hotfix is completed.
After the successful installation of the hotfix and a system restart, verify the following files.
If the following content is not available, it must be updated.
To install the hotfix
NOTE: Enable sticky session if you are hosting any site on the load balancer, as Admin, Helpdesk, and Self-service sites use session state management technique.
If it is not possible to install and apply this cumulative hotfix, you may manually update the following files to implement the fix.
Otherwise please install the hotfix and it will automatically update the files, and no further action is required.
NOTE: Before manually updating these files or before installing the hotfix, One Identity recommends to take a backup of the following files listed here.
Replace with: <httpRuntime requestPathInvalidCharacters="" targetFramework="4.6.1" />: