Forum Discussion
JD1
Altostratus
AltostratusAPM - Multiple sessions per single VS and APM profile/policy.
Hi All, I've a scenario where multiple URLs land on a policy and the result is determind by the URL originally reached. As expected though, once the policy is completed for one browser session...
It is not dedicated only to SWG, you can use with APM also to improve security of a webtop for example. When you attach a per-request policy to your VS, all your client requests are evaluated by this policy.
With a URL_branching box at the begining of the policy, you can decide what action to perform (like a new authentication) according to the URL requested by the client. The session variable to use is "perflow.category_lookup.result.url". Hope it's clear.
Nicolas_Destor
Cirrostratus
CirrostratusIt is not dedicated only to SWG, you can use with APM also to improve security of a webtop for example. When you attach a per-request policy to your VS, all your client requests are evaluated by this policy.
With a URL_branching box at the begining of the policy, you can decide what action to perform (like a new authentication) according to the URL requested by the client. The session variable to use is "perflow.category_lookup.result.url". Hope it's clear.
JD1Thanks for the reply.
- JD1
Just to update on this - This seems to be only applicable if you're using LTM_APM mode(?).
So far as I can see, if I want to apply things to connectivity resources then it's a no go.
In the end, my solution was multiple VS forwarded from a landing VS using irules and the 'virtual' command.
Each sub-VS then had an individual APM policy associated.