by ChrisH » Nov 19 03 9:08 am
Larry,
Ya, I tend to agree with you but traffic stops until client authenticates at WRS. My logic is if WRS has stopped packet waiting for authentication because it is part of WRS policy then it should "honour" the other WRS policies, but it seems if TR is enabled on WWW proxy, WRS just sends it on - doesn't check the rest of WRS policies.
This is setup I have in case this is confusing. WIN98 client, WGIC 5.1 to XP WG 5.1 server, WRS policies - user must be authenticated and a time restriction. WWW proxy, TR enabled, user can be assumed. So in this setup when client uses IE they are required to authenticate but then are able to browse. Turn off TR and policy is enforced - client unable to browse. In fact all other WRS policies are then enforced. BTW I think I uncovered a slight issue when trying this all out. If TR is not enabled and a WRS Ban List policy - "Client application name contains iexplore" is set, this Ban list policy is not followed, but if same policy is set to "NOT client application name contains iexplore" then IE is not allowed which is backwards to my way of thinking. Oh, but I'm on the other side of the world from NZ and things are sometimes reversed from Northern to Southern Hemisphere :)
Anyway, IMHO I think all WRS policies should be met before moving packet on, but maybe there is something else going on.
Chris H.