• State Suggested Answer
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 117 views
  • Users 0 members are here
Options
Related

Connection issue between Plunet and GroupShare with latest Java build

Nicol Tincani

Hi  or GroupShare developers,

Just wanted to let you know about this recent issue we have found between Plunet and GroupShare. This is the message from our Head of Support:

“The latest Java build jdk-17.0.18+8 from January breaks the connection between Plunet and Groupshare.

With this build, Java updated their security algorithms and disables more algorithms than with previous builds. As soon we disable the following, Plunet can connect with Groupshare again:

 Screenshot showing a list of disabled algorithms in Java, including SSLv3, TLSv1, TLSv1.1, DTLSv1.0, RC4, DES, MD5withRSA, and others, with comments and line breaks.

 This information should also help RWS to troubleshoot the issue.”

We are going to proactively reach out to customers using the GroupShareManager, so that they are informed about this, but it would be useful to have a reply from you.

Thank you.

Generated Image Alt-Text
[edited by: RWS Community AI at 3:10 PM (GMT 0) on 13 Mar 2026]
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi  
    Thanks for raising this issue with us. 

    From the information I could gather with Java 17 certain protocols were disabled (TLSv1 and TLSv1.1). This shouldn't affect GroupShare as we support TLS12. 
    Also, certain cipher and key exchanges were disabled and some key size constraints were put in place with Java 17. This is an industry trend, where RSA key transport is deprecated as vulnerabilities are found. 

    My understanding is that Java 17+ components/applications attempting to connect to GroupShare over HTTPS will fail with a handshake error if the server only offers these disabled cipher suites.
    The fix is server-side only - where the TLS configuration on the GroupShare server needs to be updated so that you prioritize certain cipher suites and disable the ones not supported by Java 17. This can be done using the  IIS Crypto tool.
Reply
  • 0

    Hi  
    Thanks for raising this issue with us. 

    From the information I could gather with Java 17 certain protocols were disabled (TLSv1 and TLSv1.1). This shouldn't affect GroupShare as we support TLS12. 
    Also, certain cipher and key exchanges were disabled and some key size constraints were put in place with Java 17. This is an industry trend, where RSA key transport is deprecated as vulnerabilities are found. 

    My understanding is that Java 17+ components/applications attempting to connect to GroupShare over HTTPS will fail with a handshake error if the server only offers these disabled cipher suites.
    The fix is server-side only - where the TLS configuration on the GroupShare server needs to be updated so that you prioritize certain cipher suites and disable the ones not supported by Java 17. This can be done using the  IIS Crypto tool.
Children
No Data