Unable To Access WebLogic Console on HTTPS Even Though the Default Secure Channel Is Listening
(Doc ID 1993680.1)
Last updated on DECEMBER 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.
***Checked for relevance on Dec 5, 2016***
A customer reports being unable to access the WebLogic admin console after configuring Custom Identity and Custom Trust using SHA 256 certificates.
The certificate chain in the Identity keystore looks fine (validated using the
utils.ValidateCertChain utility). From the logs we can see that the Weblogic DefaultSecure channel is listening on the SSL port specified:
The same keystore was used as both an Idenity and a Trust keystore.
The customer reported that when a SHA1 certificate keystore is used both as Identity and Trust keystore (with JSSE disabled), they do not see any issues.
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