Policy Transmission attributes not working as expected
Originally Published: 2011-08-29
Article Number
Issue
transmission attribute "is NOT" matches but event/incident is still being generated
Resolution
Select one of "From Sender", "To Recipient", "From IP", etc. using "is" or "is Not"
If additional attributes are required click on "New Rule" and add the attribute there
For example, to exclude certain trusted senders and recipients:
Add an Allow rule with From Sender and a list of trusted senders
Add an Allow rule with To Recipient and a list of trusted recipients
Place these 2 rules before the rule containing the content blades
Related Articles
RSA Via Lifecycle and Governance WildFly cluster not connecting as expected Number of Views "Maintain" and "Maintain with Expiration" are not working as expected in multi-step review in RSA Governance & Lifecycle Number of Views A revocation request executes immediately in RSA Identity Governance and Lifecycle if the revocation date is defined beyon… Number of Views Auto generated revocation requests Stuck in Fulfillment Phase with AFX errors in connector logs If any Change Item rejecte… Number of Views Generic REST EDC collector not getting the desired results in entitlement relationship in RSA Governance & Lifecycle Number of Views
Trending Articles
How to Download OTP Token Seed Files from myRSA RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8
Don't see what you're looking for?
