Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 130
  • Last Modified:

java padding exception

We have a production server (Windows 2008).  On the weekend we ran a Windows update and a java update, to the latest patch levels.  Now Java (Version 8 update 31).  Now no one can access the network over SSL.  They all get SSL exception Invalid padding length  Null pointer exception.

I backed out the java update (We're not are version 8 update 25).  Still no luck.

I'm hoping someone has run into this and can help me figure this out.
0
geekdad1
Asked:
geekdad1
  • 4
  • 3
1 Solution
 
gheistCommented:
What are the endpoints of connection that gives "invalid padding length" ?
0
 
geekdad1Author Commented:
I think the problem is with the digital certificate at the other end of the connection.  Although they feel that it is ok, I can connect to a different server on another network without problems.  So at this point I don't know what about the certificate java is complaining about but we're staying with the most recent version 7 until such time as we can confirm that we can connect successfully with that server.

If anyone knows what changed in version 8 of Java that is causing it to generate an exception where it didn't before, that would be helpful.  They said the certificate was only configured for SHA1.  Could that be part of the issue?
0
 
gheistCommented:
What are the endpoints of connection that gives "invalid padding length" ?
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
geekdad1Author Commented:
I'm not entirely sure what you are asking for.  Are you looking for URL's?
0
 
gheistCommented:
Software versions????
0
 
geekdad1Author Commented:
Our end Windows 2008 R2 standard running java 8_31
Users connect to our server via remote desktop.
Our java app connects to a remote server and posts information to it's web app.
Remote server is Unix AIX version 7.1 using Websphere 5.x

The remote servers are managed by a different organization.  If you need more detailed information for the remote end, I'll have to dig and find someone who can help.
0
 
krakatoaCommented:
Maybe the cryp strength is incorrect - 256, where it should be 128.
0
 
gheistCommented:
Websphere 5.0 does not support anything better than SSLv3
Since that was broken you must switch to http for equivalent security as you always had.
java 8_31 disabled broken protocol.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now