Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Outbound Web Service Calls Fail With "Could not generate DH keypair" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Outbound Web Service Calls Fail With "Could not generate DH keypair"
KB0563593

Outbound Web Service Calls Fail With "Could not generate DH keypair"


5301 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Web Services are becoming more secure. When TLS 1.1 or 1.2 is required by the web service that is being called, an exception is thrown if ServiceNow is using the default SSLv3 or TLS 1.0. When creating or testing an Outbound SOAP or REST Message, a message indicating that the WSDL is unable to load. 

Symptoms

Symptoms include:

  • Outbound web service calls fail:
    javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
  • Searching for the Java version in the page /xmlstats.do will show lines like the following, depending on the instance version:
    <system.java.version type="info">1.6.0_xx</system.java.version>
    <system.java.version type="info">1.8.0_152-snc2</system.java.version>

Cause

The loaded Java version (i.e. 1.6 or 1.8) does not allow for TLS 1.1 or 1.2.

For example, on the latest Jakarta patch the expected Java version should be:

<system.java.version type="info">1.8.0_161-snc1</system.java.version>

 

Resolution

ServiceNow Customer Support can upgrade the Java version of your instance. Open a case with Technical Support. Include the exact error message you received and your Java version (obtained from xmlstats.do). 

After the case has been received and reviewed, a Change record is created and can be processed at the time of your choice.

Alert iconWarning: The instance is not taken down to implement the change, however, each node in the instance requires a restart. Any users currently logged into the node must re-authenticate, so it is best to schedule the change during a low use time period.

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.