Create UserSession From SessionToken failed after applying 126.96.36.199417 bundle patch to OAM Server and Webgate
(Doc ID 2436814.1)
Last updated on AUGUST 20, 2018
Applies to:Oracle Access Manager - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Create UserSession via SessionToken works fine with 184.108.40.206 ASDK against 220.127.116.11 OAM Server and 18.104.22.168 Webgate
Constructs a UserSession object with specified token
After you applied 22.214.171.124417 to OAM Server and Webgate, the same ASDK code fails with
"Authn token is either null or invalid. "
1. Apply 126.96.36.199. BP14 on OAM Server
2. Apply 188.8.131.52. BP10 on WebGate
3. Set globalHMACEnabled and EnableHostPortValidation to false
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!