I have worked on the DLP Integration via CA SiteMinder SharePoint Agent for Content Classification on SharePoint. Hence I know that as long as CCS can return the Content Classification Response back to SiteMinder Policy Server; SiteMinder Policy Server would send the response back to SharePoint Agent whether the user is allowed to view contents within a specific document. This has been extensively used for Classification of document content (Word, excel, PDF etc). Hence in terms of Custom Classifications; Yes it should work - it does work with the OOB default classifications. When you add more Custom Classification on the CCS end, the WAM UI should be able to list all Classification from the CCS for us to allow to configure what Classification should be applied to a particular ROLE in EPM Model.

I am unsure where OR how you intend to use the CCS / DLP Integration with SiteMinder. There are caveats one needs to know....

DLP Integration is only available on EPM Model and not on Policy Domain Model. Hence if you are only using Policy Domain Model; you'll need to move the resources which need to be DLP / CCS enabled into EPM Model.

I know this works via SharePoint Agent for Content Classification on SharePoint - does it work via a normal WebAgent? I don't know; I see the disambiguate plugin present on WebAgent and SPS - however check the Support Agreement for CCS Integration Support via anything else other than CA SiteMinder SharePoint Agent. My guestimate is CCS Integration is currently supported only via CA SiteMinder SharePoint Agent for SharePoint Single Sign On. Hence please check this.

I have worked on the DLP Integration via CA SiteMinder SharePoint Agent for Content Classification on SharePoint. Hence I know that as long as CCS can return the Content Classification Response back to SiteMinder Policy Server; SiteMinder Policy Server would send the response back to SharePoint Agent whether the user is allowed to view contents within a specific document. This has been extensively used for Classification of document content (Word, excel, PDF etc). Hence in terms of Custom Classifications; Yes it should work - it does work with the OOB default classifications. When you add more Custom Classification on the CCS end, the WAM UI should be able to list all Classification from the CCS for us to allow to configure what Classification should be applied to a particular ROLE in EPM Model.

I am unsure where OR how you intend to use the CCS / DLP Integration with SiteMinder. There are caveats one needs to know....

DLP Integration is only available on EPM Model and not on Policy Domain Model. Hence if you are only using Policy Domain Model; you'll need to move the resources which need to be DLP / CCS enabled into EPM Model.

I know this works via SharePoint Agent for Content Classification on SharePoint - does it work via a normal WebAgent? I don't know; I see the disambiguate plugin present on WebAgent and SPS - however check the Support Agreement for CCS Integration Support via anything else other than CA SiteMinder SharePoint Agent. My guestimate is CCS Integration is currently supported only via CA SiteMinder SharePoint Agent for SharePoint Single Sign On. Hence please check this.

When you define a pre-calssification job you Specify the URL to a Microsoft SharePoint site or a specific document library on that site. (SharePoint 2007 with Windows SharePoint Services 3.0 or later) You can also specify individual folders within a document library. In the following example, Q1 is a folder within the Reports library:

You can also be explicit and specify which SharePoint items you want to scan.

The CCS pre-classification agent is mainly intended to classify files stored in SharePoint document libraries. Other items such as picture libraries, discussion boards, and announcements are not generally applicable to CCS pre-classification scans.

I hope this addresses your question. HubertDennis Hubert please feel free to add anything further from the SiteMinder perspective.

Currently we have tested for Doc, Excel, PDF via the E2E CA SSO solution. Having said that it may just work on Content e.g. HTML etc. a quick test would flush this out. SharePoint is a vast ocean in itself. Hence covering all aspects of the ocean does pose some challenges. Hence we test E2E on most customer preferred ones.

Also suggest opening a new thread for a new query, as it keeps the query nuclear and easy to show up on search.