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

Connecdtion to SB fails: anonymous cipher suites are within the supported list #332

Closed
eperov opened this issue Jan 30, 2019 · 11 comments
Closed
Assignees
Labels
Milestone

Comments

@eperov
Copy link

eperov commented Jan 30, 2019

Hi,
Connection to Service Bus fails with the error.
The same code works from another machines.

com.microsoft.azure.servicebus.primitives.ServiceBusException: org.apache.qpid.proton.engine.TransportException: None of [TLS_DH_anon_WITH_AES_128_CBC_SHA, SSL_DH_anon_WITH_3DES_EDE_CBC_SHA, SSL_DH_anon_WITH_DES_CBC_SHA, SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA] anonymous cipher suites are within the supported list [T LS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, TLS_RSA_WITH_AES_256_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384, TLS_D HE_RSA_WITH_AES_256_CBC_SHA256, TLS_DHE_DSS_WITH_AES_256_CBC_SHA256, TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA, TLS_ECDH_ECDSA_WITH_AE S_256_CBC_SHA, TLS_ECDH_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_RSA_WITH_AES_256_CBC_SHA, TLS_DHE_DSS_WITH_AES_256_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA25 6, TLS_RSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_RSA_WITH_AES_128_CBC_SHA256, TLS_DHE_DSS_WITH_AES_128_CBC_SHA256, TLS_ECD HE_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_128_CBC_SHA, TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA, TLS_ECDH_RSA_WITH_AES_128_CBC_SHA, TLS_DHE_RSA_WITH_AES_128_C BC_SHA, TLS_DHE_DSS_WITH_AES_128_CBC_SHA, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384, TLS_RSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384, TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_RSA_WITH_AES_256_GCM_SHA384, TLS_DHE_DSS_WITH_AES_256_GCM_SHA384, TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256, TLS _RSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256, TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_RSA_WITH_AES_128_GCM_SHA256, TLS_DHE_DSS_WITH_AES_128_GCM_SHA256], TrackingId: 0e18cf2f-b2c0-41a8-99a2-1674072600c2, at: 2019-01-29T17:02:47.036-08:00[America/Los_Angeles]

@yvgopal
Copy link
Member

yvgopal commented Feb 1, 2019

Is the JRE vesion same on both machines? The SDK relies on default Java provider for security.

@yvgopal yvgopal self-assigned this Feb 1, 2019
@eperov
Copy link
Author

eperov commented Feb 1, 2019 via email

@yvgopal
Copy link
Member

yvgopal commented Feb 1, 2019

Please check your java security configuration. It is a bug or anything. On that machine, may be you are using a different security provider.

@eperov
Copy link
Author

eperov commented Feb 4, 2019

java.security files are original, no manual changes.
The list of security provides seem identical.

@nikesh-devaki
Copy link

nikesh-devaki commented Feb 8, 2019

@eperov Is it resolved?

I am also facing same issue. Same application works fine on another machine. In my case jre versions are different across machines.
(build 1.8.0_201-b09), (build 1.8.0_191-b12)

@yvgopal Is there any else we are missing?

Update: This issue is happening across all our apps and for all new instances with jre build: 1.8.0_201-b09. Downgraded jre to 1.8.0_191-b12 build to fix it.

@eperov
Copy link
Author

eperov commented Feb 8, 2019

The problem is resolved by downgrading Java from 1.8.0_201 to 1.8.0_191.

@yvgopal
Copy link
Member

yvgopal commented Mar 2, 2019

It is because JRE 8 update 201 disabled some anonymous cipher suites used by ProtonJ. This issue is fixed in the newer version of ProtonJ. SDK version 1.2.9 switched to newer ProtonJ version, which doesn't throw this error. So this issue is already fixed in version 1.2.9 and later.

@yvgopal yvgopal closed this as completed Mar 2, 2019
@yvgopal yvgopal added this to the 1.2.9 milestone Mar 2, 2019
@satish8784
Copy link

Version 1.8.0_191 seems to be expired as per Oracle website, any alternative solution to this?

@yvgopal
Copy link
Member

yvgopal commented Apr 3, 2019

@satish8784 Switch to Service Bus SDK version 1.2.9 or later.

@spenc53
Copy link

spenc53 commented Apr 4, 2019

I have updated the version of our service bus sdk to 2.0.0 but am still having this issue

@yvgopal
Copy link
Member

yvgopal commented Apr 4, 2019

If you update to newer version of the SDK, then you will get a new jar of proton-j that is 0.31.0. Maven will automatically pull it for your development. Check your application's classpath.

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

No branches or pull requests

5 participants