Total Pageviews

Friday, September 16, 2022

2nd OAM server in cluster unable to process the request OAM_JSESSIONID

SYMPTOMS Oracle Access Manager acting as the Service Provider (SP)WLS Managed Server Cluster with 2 OAM ServersOHS proxing mod_weblogic. There is no issue if only one WLS managed server is running When both WLS managed servers running OAM are started, the Federation flow fails. CAUSE Configuration of OHS server for mod_weblogic for OAM. The "WLCookieName" parameter for the OHS server configuration is missing or has the wrong value. In this specifc case the value was incorrect, OAMSESSIONID, where as the OAM application uses "OAM_JSESSIONID". The above fix the issue that two wls_oam1/wls_oam2 could not be started for federation to work.

Wednesday, September 14, 2022

JDK updated error jdk-8u341-linux-x64 :Caused by: java.net.URISyntaxException: Malformed IPv6 address at index 8

After updating JDK to new version jdk-8u341-linux-x64, IDM components are not coming up. It is a bug. here is how i fixed it error error:Caused by: java.net.URISyntaxException: Malformed IPv6 address at index 8 I have eadded below value to setDomainEnv.sh JAVA_PROPERTIES="-Dcom.sun.jndi.ldapURLParsing=legacy Also i have added above attribute to each Manager server Start stop section in Arguments section -Dcom.sun.jndi.ldapURLParsing=legacy