Protect the SharePoint Shared Services Provider (SSP) and My Sites with FBA › How to Protect the SharePoint SSP with SiteMinder r12.0 SP2 and FBA

How to Protect the SharePoint SSP with SiteMinder r12.0 SP2 and FBA

If you are using a SharePoint server in your organization and you want to protect the SSP with SiteMinder, use the following process:

Note: Not required if you are using Windows SharePoint Services instead of a Microsoft Office SharePoint server.

1. Verify the port numbers of the following SharePoint web sites:
   • The Central Administration web site
   • The Default SSP web site
2. Extend the default SSP web site to another zone.
3. Change the alternate access mapping of the extended SSP web site to use a fully qualified domain name (FQDN).
4. Do one of the following tasks:
   • Add the SiteMinder ISAPI filter to the IIS 6.0 web site for your Extended SSP.
   • Add the SiteMinder ISAPI filter to the IIS 7.x web site for your Extended SSP, and then add the Handler Mapping for the IIS 7.x web site for your Extended SSP.
5. Edit the web.config file of your extended SSP web site to include the following items:
   • CA Membership provider
   • CA Role provider
   • HTTP Session Manager Provider
   • Forms Authentication settings

   Note: The CA in the Agent for SharePoint code for the web.config files stands for CA Technologies. In these examples, it does not mean SharePoint Central Administration. The related procedures explain where to add the code.

6. Do one of the following tasks:
   • Add the SiteMinder ISAPI filter to the IIS 6.0 web site for your default SSP.
   • Add the SiteMinder ISAPI filter to the IIS 7.x web site for your default SSP, and then add the Handler Mapping for the IIS 7.x web site for your default SSP.
7. Edit the web.config file of your default SSP web site to include the following items:
   • CA Membership provider
   • CA Role provider
   • HTTP Session Manager Provider
   • Forms Authentication settings
8. Use the SharePoint Central Administration UI to do the following tasks:
   1. Change the Authentication provider of your default SSP site to Forms.
   2. Change the alternate access mapping of the default SSP web site to use a fully qualified domain name (FQDN).
   3. Add a SiteMinder user under personalization permissions.
   4. Make the SiteMinder user from the previous step a site collection administrator for the default SSP site.
9. Use the Administrative UI to create an application and policy to protect the SSP URL.
10. Use the SharePoint Central Administration UI to change the Authentication provider of your default SSP site to Forms.
11. Rename the following sections in the web.config file of your extended SSP web site:
    • CA Membership provider
    • CA Role provider
12. Use the SharePoint Central Administration UI to change the names of the items in Step 12 on the Authentication provider page of your extended SSP site.

More information:

SiteMinder Agent for SharePoint SSP Protection Worksheet

How to Protect My Sites with SiteMinder (all versions)

Protect Applications with the SiteMinder Agent for SharePoint