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.
An error was discovered processing the WS-Security header during MID Server Installation - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • An error was discovered processing the WS-Security header during MID Server Installation
KB0826978

An error was discovered processing the WS-Security header during MID Server Installation


4313 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

  • Observed the below error during mid server installation.

     ENV:Fault><faultcode>wsse:InvalidSecurity</faultcode><faultstring>An error was discovered processing the WS-Security header</faultstring><detail>Invalid Security Policy Selected. Select a Inbound policy for Inbound  Requests</detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

     (810) Thread-4 WARNING *** WARNING *** SOAP server error reported by ServiceNow instance, user 'midserverqa3@accenture' may be missing the 'soap_script' role

     (816) Thread-4 DEBUG: Event: StartupTestResultEvent

Release

  • All

Resolution

  • The listed error messages are encountered are with respect to a WS-security SOAP message.

  • We come across these errors when the value of the property "Require WS-Security header verification for all incoming SOAP requests" is set to "Yes" from the default OOB value of       "No".

  • This property can be visible under Navigator > System Web Services > Properties

  • Changing the value of the above property to "No" should help fix the issue with the installation.

Related Links

  • Please refer the  Product Documentation for more details.




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?

Attachments

Attachments

  • Screenshot 2020-06-01 at 5.55.58 PM.png

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.