To implement CD SSO, Do we have to get .ccc file from CA or will it come with SPS itself?, because I don't see any .ccc file under my installation directory.
If I understand your question correctly, I believe you are trying to configure Cross Domain SSO (CD SSO) and are looking for the Cookie Provider file (SmMakeCookie.ccc) ?
SmMakeCookie.ccc is a directive and not a physical file. That is the reason why you can't find it inside the instllation directory.
More about Cookie provider and how it should be configured (from the Policy Server Admin Guide ):
Reference : https://support.ca.com/cadocs/0/CA%20SiteMinder%20r12%205-ENU/Bookshelf_Files/HTML/idocs/index.htm?toc.htm?1855337.html?zoom_highlight=cookie%2Bprovider
To have the other agents in your SSO environment use a cookie provider, specify the location of the agent that is acting as a cookie provider with the following parameter:
Specifies the URL of the web server where the agent that is acting as the cookie provider resides.
A cookie provider is an agent in a single sign-on environment. The cookie provider sets a browser cookie for the local domain in which it exists. After this cookie is set, users can navigate throughout the single sign-on environment without reauthenticating.
The cookie provider name requires a .ccc extension, as shown in the following examples:
Default: No default
Example: (IIS, Oracle iPlanet, and Domino web servers) http://server1.example.com:80/siteminderagent/SmMakeCookie.ccc
Example: (Apache and Apache-based web servers) http://server1.example.com:80/SmMakeCookie.ccc
Limits: This parameter requires a fully qualified domain name.
Hope this helps.
Did that answer your query ? If it did, could you please mark this discussion as Answered.
I have configured Cross Domain in my enviornment and now when I'm trying to access the application (which I made as a cookie provider) working fine but when I access the other domain application; it is stucking up at http://server1.example.com:80/siteminderagent/SmMakeCookie.ccc page.
However i can find in smaccess.log file that user got authenticated and authorized sucessfully on other domain application.
Retrieving data ...