Users Unable To Authenticate After Upgrading Logon Manager From 188.8.131.52.0 To 184.108.40.206.3.1
(Doc ID 2282067.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Enterprise Single Sign-On Suite Plus - Version 220.127.116.11.1 to 18.104.22.168.1 [Release 11g]
Information in this document applies to any platform.
***Checked for relevance on 05-DEC-2018***
Oracle Enterprise Single Sign-On Logon Manager 22.214.171.124.1
Users are unable to authenticate and decrypt their ESSO credentials from the repository after upgrading from 126.96.36.199.2 on Windows 7 to 188.8.131.52.1 on Windows 10. On the Windows 7 platform the ESSO-LM 184.108.40.206.2 client is configured to use AES (256-bit) as the encryption algorithm for storing the credentials. On the Windows 10 platform, the ESSO-LM 220.127.116.11.1 client is configured to use the default AES(MS-CAPI) algorithm.
Users that are upgraded from ESSO 18.104.22.168.2 to 22.214.171.124.1 are expected to be able to authenticate and access their ESSO credentials on Windows 10 after completing the upgrade.
STEPS TO REPRODUCE
The issue can be reproduced at will with the following steps:
- Upgrade ESSO client from 126.96.36.199.x to 188.8.131.52.1 on Windows 7
- Logon to Windows 10 platform and install ESSO 184.108.40.206.1
- Restart the Windows 10 and attempt to authenticate with the AD password in the ESSO Logon prompt.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document