SAP PE SOAPUI web service 403 ModSecurity Action

After migration to SAP PE cloud. ABAP Http is not surposed any more.

So we need to change to https for all the interface.

But SAP provider service web service returen error  403 ModSecurity Action in SOAP UI test.

Solution:

  1. Ping the address, works.
  2. Telnet the port for https, works.
  3. Set the interface value to inital, works.
  4. Set the interface value field to format as designed, error  403 ModSecurity Action

After folloer the error in FILLDER, we find the reason is because:

ModSecurity is an open source, cross-platform web application firewall (WAF) module. https://modsecurity.org/about.html

So whenever you see the 403 (ModSecurity Action), this means that the mod security firewall has blocked the request. The probable cause could be vulnerable data present in the posted data, or the it could be because of the URL posted as parameter or it could be JavaScript.

In above case, the ModSecurity might have deemed the input as SQL Injection attack and hence may have blocked it. If you look into the logs of the firewall it may give you the detailed explanation.

So, Ask SAP cloude network Team to change the setting of WAF.

Tired of this stranger things in cloude project…

About me:

This post is come from www.hot583.com, you can share it with the post  original link for free.

微信原文《The End》

今日热点在看SAP HOT583

 

1人评论了“SAP PE SOAPUI web service 403 ModSecurity Action”

评论区已关闭。