Support

 Hi
Were are using Mniorange SSO component, and when we login in on joomla site it works, but then when we log out, it returns a 403 error
I was wondering if you have any thoughts as to why this happens. (The IP in the log entry is local, I know, but this happens on any server we have this located on)

Thanks.

Here is the log entry in breaches log:

-------------------------------------------------------------------------------
Blocking reason: dfishield
-------------------------------------------------------------------------------
Date/time : 2017-04-12 10:47:03 GMT
URL : https://colorconcms.wilddogdevelopment.com/?morequest=acs
User : Guest
IP : 192.168.1.1
Country : (unknown country)
Continent : (unknown continent)
UA : Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
Hash : post
Variables :
Array
(
[RelayState] => /
[SAMLResponse] => PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiPz4KPHNhbWwycDpMb2dvdXRSZXNwb25zZSBEZXN0aW5hdGlvbj0iaHR0cHM6Ly9jb2xvcmNvbmNtcy53aWxkZG9nZGV2ZWxvcG1lbnQuY29tLz9tb3JlcXVlc3Q9YWNzIiBJRD0ia2xiaW9laG5mZmpkb2ZnZWJtcGFrYW9paWpoYWNjaGhlbWtrbGtlaiIgSW5SZXNwb25zZVRvPSJfNDEwZjU3NGVmMzZjZGFlOGE5NTEyODdjM2E1MWQ2OGFjNjkxNzExN2I3IiBJc3N1ZUluc3RhbnQ9IjIwMTctMDQtMTJUMTA6NDc6MDMuMTcxWiIgVmVyc2lvbj0iMi4wIiB4bWxuczpzYW1sMnA9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDpwcm90b2NvbCI+PHNhbWwyOklzc3VlciBGb3JtYXQ9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDpuYW1laWQtZm9ybWF0OmVudGl0eSIgeG1sbnM6c2FtbDI9InVybjpvYXNpczpuYW1lczp0YzpTQU1MOjIuMDphc3NlcnRpb24iPmNvbG9yY29uPC9zYW1sMjpJc3N1ZXI+PHNhbWwycDpTdGF0dXM+PHNhbWwycDpTdGF0dXNDb2RlIFZhbHVlPSJ1cm46b2FzaXM6bmFtZXM6dGM6U0FNTDoyLjA6c3RhdHVzOlN1Y2Nlc3MiLz48L3NhbWwycDpTdGF0dXM+PC9zYW1sMnA6TG9nb3V0UmVzcG9uc2U+
)


Any

Thanks for your reply.

When I try one or both query parameters per your instructions, I get this error then:

0 - Call to a member function getSignatureData() on boolean

Does that point to it is getting past the WAF and now it is a different issue with a different component?

Also get that same error when disabling dfishield altogether.

No worries, thanks for your replies that confirmed what we needed to test, and glad to rule out admin tools as the problem.
Best