uni
Sep 09, 2015Altostratus
APM policy sets pool in second virtual
I have encountered some behaviour I don't understand. I've not done much with APM until recently, so am curious to know whether I misunderstand the behaviour and there is perhaps a bug.
I have two virtual servers (vs1 & vs2) with two Access Profiles (ap1 and ap2), sharing the same AAA server profile, SSO profile and domain cookie. ap1 may set the pool in the policy, ap2 never does.
If a user accesses and authenticates via vs1 and the pool is set, then accesses vs2, vs2 sends traffic to the pool set in vs1.
Is this expected behaviour? I can't imagine how this could be the case.