Forum Discussion
CirrostratusIntegrate mobile application with WAF
CirrostratusActually I have test that with ASM (not blocking mode) , but I noticed that the public ip does not reach the backend server. Cuz the first page in app is a login page, when I try to enter my user and pass there is a message show "user name or pass not correct" this is when the public ip placed in api url . But when i replace public ip with the backend ip in api url the app works fine.
The idea from adding public ip in api url is to pass traffic through WAF and that public ip should reach the backend ip . I don't know of this the way doing that or not.
Thanks
Cirrostratuswithout WAF it is working fine since the server ip is placed in api url..
my scenario is , i want to protect my application with WAF , i follow the normal process i have create virtual server , node, pool , policy ..
i have assign public ip in virtual server , placed server ip in node and assign it to pool , then assign pool to virtual server with policy, and the change i did i have replace server ip with public ip in api url ex:
old api url : https://10.x.x.x/api
new api url : https://82.x.x.x/api
82.x.x.x : it is the public ip in virtual server.
but this scenario does not work.
the app idea , is you have to login then you can request for annual leave .
but when i start the integration with WAF , when i try to access the app by enter username and password it show error and can not verify user/password.
and there is no block in WAF block mode not applied . so i think because i placed public ip in api url and that is why can not reach server.
