Java 1.8.0_351 throws unsupported keytype during Window Native Authentication
(Doc ID 2915455.1)
Last updated on DECEMBER 15, 2022
Applies to:
Oracle Access Manager - Version 12.2.1.4.0 to 12.2.1.3.220405 [Release 12c]Information in this document applies to any platform.
Symptoms
After installing JDK 1.8.0_351, user authentication with Windows Native Authentication (WNA) failure.
OAM server .out file report "Found unsupported keytype (##)"
Found unsupported keytype (23) for HTTP/<host1.domain1>@<domain1>
Found unsupported keytype (3) for HTTP/<host1.domain1>@<domain1>
Found unsupported keytype (1) for HTTP/<host1.domain1>@<domain1>
<Error> <oracle.oam.controller> <OAM-02010> <User account is locked. Authentication failed.>
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 |
Cause |
Solution |
References |