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 directories on a Datacenter agent - RSA DLP 22Number of Views How to exclude RSA Authentication Manager 8.x from picking up disabled user account data from the Microsoft LDAP directory 161Number of Views Users from an external identity source are listed as disabled in the RSA Authentication Manager 8.x Security Console 229Number of Views Error 1316. The specified account already exists when running RSA Authentication Agent 7.x for Windows update_x64.exe 638Number of Views Archive Logs Using Schedule Log Archival 154Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide