Categories
- All Categories
- Oracle Analytics Learning Hub
- 19 Oracle Analytics Sharing Center
- 18 Oracle Analytics Lounge
- 232 Oracle Analytics News
- 44 Oracle Analytics Videos
- 15.9K Oracle Analytics Forums
- 6.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 87 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OAS 7.6 SSL configuration issue
Hello All,
We did fresh installation and configuration for OAS 7.6 everything worked perfect.
tried to implement SSL configurations and updated nodemanager.properties and console (Adminserver & managed server -Keytools & SSL tabs) used below document for reference.
OBIEE 12c/OAS: How To Configure SSL Including Examples (Doc ID 2188982.1)
while restarting services getting below error.
<Oct 9, 2025 11:48:51 AM EDT> <Info> <Security> <BEA-090909> <Using the configured custom SSL Hostname Verifier implementation: weblogic.security.utils.SSLWLSHostnameVerifier$NullHostnameVerifier.>
Unable to connect to running NodeManager on host: xxxxx, due to: Error occurred while performing nmConnect : Cannot connect to Node Manager. : sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Use dumpStack() to view the full stacktrace :
Fatal: Failed to start one or more Servers (return 3)
Any suggestions to fix this issue?
Thanks,
Suresh.
Answers
-
Hi,
Welcome to the Oracle Analytics community and forum.Where does your SSL certificates come from? Who is the signer? If it isn't a publicly accepted CA, did you import the CA certificate in the default trust keystore?
If you search in MOS the error you posted, you will find a number of results with that same error. Various products, but all based on WebLogic, and therefore they all give you hints of things to verify to solve your issue.
1 -
Suresh,
We've had this similar issue - and two things to check. Ensure that your SSL Certificate is properly signed. We had self-signed through our domain and they weren't acceptable. Needed to be from a proper CA.
Also - check the alias' are included into the java keystore as well. (That pesky other keystore for the trust cacerts).
1 -
Suresh,
As an aside curiosity question, why the new installation of OAS 2024 (7.6) and not OAS 2025 (8.2)?0 -
I had a similar issue as well. To resolve it, I changed the Hostname Verification from BEA Hostname Verifier to blank for both the Admin & BI server in the Advanced section of the SSL tab.
1
