It seems, that there is not automatically generated a URL hardening exception for the required paths to display the login form webpage, therefor it will be blocked from URL Hardening due "invalid signature" ;o)
It seems, that the used paths for the form are generated by some logic as the according virtual server:
/REF_RevAutOwassoform/company_logo.png
and the used realm - which looks quite confusing in my case [:S]
/Guess%20what...failed%20logins%20will%20be%20traced%20back..._form
However: Manually placing those two paths into a URL hardening exception for the webserver brings the form based auth window back to life...
Those required exceptions should be created automatically in the backend if URL hardening is active. [:D]
Guest User!
You are not Sophos Staff.
