Not able to select EDM as a directory
search cancel

Not able to select EDM as a directory

book

Article ID: 451290

calendar_today

Updated On:

Products

Data Loss Prevention Core Package

Issue/Introduction

We have a policy that contains a rule:
Also Match: Sender User Based on a Directory From <example EDM>

We are trying to create a new policy that is similar using a new EDM we just created, however after creating the EDM when we try to select the newly created EDM it is not available in the pull down for " Sender/User Matches Directory From <example EDM>. 

Cause

When creating the EDM and you get to the field mappings section you must map to the appropriate system fields for the data type being used.

In this case, the email field had been mapped to a custom field called "mail" The Enforce server will not recognize custom fields as being system fields, and if the email field is not populated it will not be recognized as a valid sender or recipient pattern.

As with AD groups certain fields are mandatory such as:

FIRST_NAME: First name (mandatory)
LAST_NAME: Last name (mandatory)
EMAIL: Email address (mandatory if Login not present)
LOGIN: Login of user in DOMAINLOGIN format (mandatory if Email not present)

 

 

 

Resolution

Recreate the EDM selecting the appropriate system fields for the user information.

Please note:

Be sure to use the appropriate fields for the type of response rule this is intended for.

Example if it is an email response rule you will want to make sure the email field is populated, whereas if it is a web prevent policy the DOMAINLOGIN format would likely need to be used.