Exchange auto discover

Question

Hi, 
 i wish you all a happy new year, 
 since we started using XGS2100 appliances with version SFOS 19.0.1 MR-1-Build365, have we noted some problem 
 like Auto discover is blocked. 
 i am trying to call the auto discover service but web application blocked it, 
 that leads to some problem like teams calendar are disappeared because of this issue. 
 i hope that i find the support for this case

Vivek Jagad · Accepted Answer

So, under on Sophos Firewall Web-admin > PROTECT > Web server > Protection policies > Exchange AutoDiscover > Open

And refer the following guide !
Add a web server protection (WAF) rule - https://docs.sophos.com/nsg/sophos-firewall/19.0/Help/en-us/webhelp/onlinehelp/AdministratorHelp/RulesAndPolicies/WebServerProtection/WAF/Rules/WAFRuleAdd/index.html

Vivek Jagad · Answer

Hello leo leo , Thank you for reaching out to the community, in that case you can always create an exception for the exchange auto discover .

Vivek Jagad · Answer

The reason here is Static URL Hardening, no signature found. 
 It would be best practice to always enable both URL hardening and form hardening because those two functions are complementary, especially in the way that they prevent issues you may have when enabling just one of them:
 
 Only form hardening is activated: When a webpage contains hyperlinks with appended queries (which is the case with certain CMSs), e.g. example.com/ , such page requests are blocked by form hardening because it expects a signature, which is missing. 
 Only URL hardening is activated: When a web browser appends form data to the action URL of the form tag of a web form (which is the case with GET requests), the form data becomes part of the request URL sent to the webserver, by that rendering the URL signature invalid.

The reason why activating both functions solves those issues is that in case either form hardening or URL hardening find that a request is valid, the WAF accepts the request.

Exchange auto discover

Top Replies