URL Policy Agent/Portal not for gateway

Question

Consider LDAP (for intranet) and Radius (for intranet).
We would like to limit the access to certain URL's based upon the authentication scheme.
To do this we've created a policy:
URL Polict Agent URL=X and Authentication Radius OK from IP Internet
URL Polict Agent URL=X and Authentication LDAP OK from IP Intranet
It seems that the URL policy is not taken into account by the gateway or rewriter proxy for that matter.
Does this kind of policy only work if i'm accessing a webserver or proxy using the identity plugin?

Answer 1

The custom authentication module.... Does it determine what type of authentication to present to the user based on IP? E.g. LDAP or SecurID?
This is confusing me a bit - maybe just the term authentication module..... I'm currently thinking of it as another Service listed under the Authentication leaf of the left-hand-side of IdS AdminUI (Services or Identity Management -> Services). As I understand it - something else in the IdS triggers which module to use, or the module is requested in the URL.
Thus if the URL doesn't contain the module name, it would seem something in the Organizational auth config or a Policy Condition (Subject IP?) would trigger an authentication type based on source IP.
Since authnetication chaining causes problems with fall-through rather than executing lock-out, we use the SecurID & DS passcode/password services respectively, not IdS password reset (which we will implement in Lighthouse self-service capabiltity... later)
The result is either SRA/GW or IdS will need to select the auth module from the Source IP in the packet.
So you might see my confusion when referencing a custom auth module....