Oracle Access Manager (OAM) - Login Fails "Malformed IPv6 address at index ..." After The JDK Was Updated with Java April 2022 CPU ( JDK 1.8 Update 331 or JDK 1.7 Update 341 )
(Doc ID 2865793.1)
Last updated on APRIL 15, 2024
Applies to:
Oracle Virtual Directory - Version 12.2.1.4.0 and laterOracle SOA Suite - Version 12.2.1.3.0 to 12.2.1.3.0 [Release 12c]
Oracle Access Manager - Version 11.1.2.3.0 and later
Information in this document applies to any platform.
Symptoms
Updated Java with April 2022 CPU (JDK 1.8 update 331 or greater ... JDK 1.7 update 341 or greater) .
- Now login fails with
or
or
or
|
- From the WLS Admin diagnostics log file ...
- It has also been reported that LDAP users are able to log into the application, but are not getting their associated group memberships. The <server>-diagonistc.log file does not show the API making the group membership query. It does appear that it is making the initial user query but isn't returning user attributes.
- Reverted the JDK back to "Java SE 8 Update 3321" and the issue does not reproduce.
- Added "com.sun.jndi.ldapURLParsing=legacy" to Server startup for OAM Admin and Managed Server, this exception is no longer seen.
Changes
Applied the Java April 2022 CPU , namely JDK 1.8 update 331
This could also be seen with OAM 11.1.2.x with JDK 1.7 update 341
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |