When configuring Exchange Mailbox Message Delivery Restrictions (e.g., "Only senders in the following list") using PolicyXpress, applying an account's Distinguished Name (DN) to the eTADSauthOrig attribute fails with an "Invalid JSON data" error. This occurs because the policy requires a specific JSON object format rather than a raw DN string.
Identity Manager 14.x
The eTADSauthOrig attribute in PolicyXpress requires a JSON-formatted string that maps the account object, rather than a standard distinguished name (DN). Providing a DN string directly results in a validation failure during policy execution.
To successfully configure the eTADSauthOrig attribute, you must pass a JSON string containing the account details.
Identify the location of the account within your Active Directory environment.
Format the eTADSauthOrig attribute using the following JSON structures based on the account path:
For accounts in an Organizational Unit (OU): {"name":"Account=testuser,ADSOrgUnit=TestOU,EndPoint=TestADS,Namespace=ActiveDirectory,Domain=im,Server=Server"}
For accounts in a Container (CN): {"name":"Account=testuser,ADSContainer=Users,EndPoint=TestADS,Namespace=ActiveDirectory,Domain=im,Server=Server"}
To speak with a customer representative or a Support Engineer see . Scroll to the bottom of the page and click on your respective region.