The rules.xml file can be used to exclude resources based on a URL that matches a regular expression. To exclude URL's using the rules.xml file you must create a rule with an argument type of "URI" and with an expression argument that contains a regular expression that matches the URL you wish to exclude. The action type for the rule should be of type "HTTP" with an argument to return the http result "200" for any URL that matches the rule. This will cause the RSA Access Manager Agent to abandon processing of any URL that matches the expression and issue the http request immediately.
An example of a rule that allows access to any aspx pages in any directory or sub directory under the home directory:
<Rule>
<argument type="URI" expression=" ^/home/*\.aspx"/>
<action type="HTTP" argument="200"/>
</Rule>
WARNING: The regular expression engine is very powerful. Ensure that the regular expression you create is carefully crafted only to exclude only he desired resources. It is very easy to unintentionally create a regular expression that matches resources you do not intend to exclude. The regular expression is not a URL, it is a substring that may match an part of the URL.
For example the rule <argument type="URI" expression="home"/> would match
/home/user1/index.html
but it also matches
/root/homepathy/secret.html
The Access Manager agent parses the incoming URL into a URI and a querystring component before applying rules. If you wish to match the incoming URL based on the querystring portion of the URL then you should use a rule with an argument type of "querystring".
For example the rule <argument type="querystring" expression="home"/> would match
/root/bin/getdir.aspx?value=home
or
/root/bin/getinfo.aspx?home=Idaho
Related Articles
How to exclude a range of IPs from analysis with whitelists in RSA Web Threat Detection 31Number of Views How to hide or disable the Set Out Of Office button in RSA Identity Governance & Lifecycle 46Number of Views Exclusion in workflow approval node not working if Out Of Office is set for an approver in RSA Identity Governance & Lifec… 57Number of Views Oracle Database Collector fails with "ORA-01017:invalid username/password" in RSA Identity Governance & Lifecycle 220Number of Views Activity Node Excludes Previous Approvers Without Exclusion Settings in RSA Governance & Lifecycle 6Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device RSA-2024-13: RSA Authentication Agent for Microsoft Windows Security Update RSA ID Plus Free Trial Playbook RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 9.0 for Apache Installation and Administration Guide