Unable to add the Data Loss Prevention (DLP) as an Integrated Product Symantec Protection Center 2.x (SPC)

Article:TECH137486  |  Created: 2010-08-09  |  Updated: 2013-04-16  |  Article URL http://www.symantec.com/docs/TECH137486
Article Type
Technical Solution


Issue



When attempting to the Data Loss Prevention (DLP) to the Integrated Products Symantec Protection Center 2.x (SPC) product, it fails.


Error



When attempting to test the connection, the following error is received:

Connection Failed: Unexpected exception occurred, please check logs for details. 


Cause



This error is seen when using an incorrect format for the username and password.


Solution



In SPC 1.0 and SPC 2.0 (2.0.0.419/2.0.1.525) DLP uses the format of  "role name\user name"  to login.
In SPC version 2.1 (2.1.0.2075) this behavior was changed, and the role should be left off. Only the username should be used. This means you need to assign the rights for DLP integration to a users "Default" role.

Integration Format: (SPC 1.0, 2.0)

To integrate DLP and SPC, use the following syntax in the username field:

<role>\<username>
or
<role>\<username>:<DOMAIN>
or
<username>:<DOMAIN>

Example: role\user:THE.DOMAIN.COM. 

NOTE:  The domain needs to be in all uppercase. This is used when you have Active Directory integration in use in DLP.

Integration Format: (SPC 2.1)

To integrate DLP and SPC, use the following syntax in the username field:

<username>

------------
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec is committed to product quality and satisfied customers.
This issue is currently being considered by Symantec to be addressed in the next major revision of the product. There are no plans to address this issue by way of a patch or hot fix in the current or previous versions of the software at the present time. Please note that Symantec reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability.  Symantec’s plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please refer to the following Web site:
http://www.symantec.com/business/index.jsp

 

 

 



Article URL http://www.symantec.com/docs/TECH137486


Terms of use for this information are found in Legal Notices