Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Connection to IBM WebSphereSIB with securityEnabled=true failed #132

Open
Zeidl opened this issue Apr 19, 2022 · 5 comments
Open

Connection to IBM WebSphereSIB with securityEnabled=true failed #132

Zeidl opened this issue Apr 19, 2022 · 5 comments

Comments

@Zeidl
Copy link

Zeidl commented Apr 19, 2022

Specifications

  • JMSToolBox version: v5.13.0
  • OS (Name, version, 32/64bits): Windows 10 64bit
  • Q provider (kind, version) : IBM WebSphereSIB (WAS ND v8.5.5.19 with global security enabled)

Expected Behavior

With connection preference "Trust all server certificates..." selected, aJMSToolBox connects to the specified SIB, queues are visible everything works fine.
Session properties are configured according to "ssl enabled" (providerEndPoints, targetTransportChain) and a truststore in jks format is provided via property javax.net.ssl.trustStore.
A connection attempt with preference "Trust all server certificates..." deselected might work.

Actual Behavior

With "Trust all server certificates..." deselected the connect attempt fails with "SunCertPathBuilderException: unable to find valid certification path to requested target".

Steps to Reproduce the Problem

  1. Deselect "Trust all server certificates..."
  2. Apply and Close -> triggers restart of JMSToolBox
  3. Try to connect

Logs

jmstoolbox.log
eclipse.log

Certificates in this WebSphere cell are self-signed.
Does this mean, that connections can only be created with "Trust all server certificates..." selected?

@titou10titou10
Copy link
Contributor

Did you solved your problem?

@Zeidl
Copy link
Author

Zeidl commented Mar 21, 2023

I found no way to create a connection using these WebSphere keystores.
But for my purposes the workaround (select "Trust all server certificates...") is sufficient.

@Zeidl Zeidl closed this as completed Mar 21, 2023
@titou10titou10
Copy link
Contributor

Maybe it is related to #146 ?
If you have the oopportunity, could you try with JTB v5.4.0? If it works, I could do the same fix
I do not have here setup to test it myself here

@Zeidl
Copy link
Author

Zeidl commented Mar 23, 2023

Great. That is indeed the cause. With version 5.4.0 the connection worked.

@titou10titou10
Copy link
Contributor

thanks!
I'll apply the same patch I've done for OpenLiberty to WAS SIB...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants