Users Unable To Authenticate After Upgrading Logon Manager From 220.127.116.11.0 To 18.104.22.168.3.1
Last updated on JULY 03, 2017
Applies to:Oracle Enterprise Single Sign-On Suite Plus - Version 22.214.171.124.1 to 126.96.36.199.1 [Release 11g]
Information in this document applies to any platform.
Oracle Enterprise Single Sign-On Logon Manager 188.8.131.52.1
Users are unable to authenticate and decrypt their ESSO credentials from the repository after upgrading from 184.108.40.206.2 on Windows 7 to 220.127.116.11.1 on Windows 10. On the Windows 7 platform the ESSO-LM 18.104.22.168.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 22.214.171.124.1 client is configured to use the default AES(MS-CAPI) algorithm.
Users that are upgraded from ESSO 126.96.36.199.2 to 188.8.131.52.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 184.108.40.206.x to 220.127.116.11.1 on Windows 7
- Logon to Windows 10 platform and install ESSO 18.104.22.168.1
- Restart the Windows 10 and attempt to authenticate with the AD password in the ESSO Logon prompt.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms