The Policy Server authenticates and authorizes users who request access to the resources in your SharePoint environment. The Policy Server stores items that you create to define the users in your SharePoint environment and the resources that you want to protect with CA SiteMinder®.
The following illustration describes the configuration process that prepares your Policy Server for use with the CA SiteMinder® Agent for SharePoint:
Follow these steps:
Change the objects on your Policy Server by opening the Administrative UI.
Follow these steps:
https://host_name:8443/iam/siteminder/adminui
Specifies the fully qualified Administrative UI host system name.
Note: If your superuser account password contains dollar‑sign ($) characters, replace each instance of the dollar-sign character with $DOLLAR$. For example, if the CA SiteMinder® superuser account password is $password, enter $DOLLAR$password in the Password field.
You can create (or duplicate) a Host Configuration object.
Follow these steps:
Important! Do not directly modify and use the DefaultHostSettings object. Always copy this object and then modify it.
Policy Server clusters are defined as part of a Host Configuration Object. When a CA SiteMinder® agent initializes, the settings from the Host Configuration Object are used to setup communication with Policy Servers.
Note: For more information about Host Configuration Objects, see the Web Agent Configuration Guide and the Policy Server Configuration Guide.
Follow these steps:
The Cluster Setup section opens.
Note: You can click Help for a description of fields, controls, and their respective requirements.
The Policy Server appears in the servers list in the Current Setup section.
Your return to the Host Configuration dialog The Policy Server cluster is listed in a table.
If the percentage of active servers in the cluster falls below the percentage you specify, the cluster fails over to the next available cluster in the list of clusters. This setting applies to all clusters that use the Host Configuration Object.
Important! The Policy Server specified in the Configuration Values section is overwritten by the Policy Servers specified in a cluster. This Policy Server is no longer used because a cluster is configured. For the value of the Policy Server parameter in the Configuration Values section to apply, do not specify any Policy Servers in a cluster. If clusters are configured, and you decide to remove the clusters in favor of a simple failover configuration delete all Policy Server information from the cluster.
Agent act as policy-enforcement points (PEPs), by intercepting user requests for SharePoint resources and communicating with the Policy Server. Agent objects associate the protected resources on your SharePoint servers with the CA SiteMinder® policies that protect those resources.
Follow these steps:
The Create Agent screen appears.
The Create Agent: screen appears.
The agent object is created and a confirmation screen appears.
If you have multiple Agent Objects in your CA SiteMinder® environment, you can place them in agent groups. Agent groups make managing large numbers of agent objects easier.
Follow these steps:
Note: If you are an experienced CA SiteMinder® user, you can add your agent objects to an existing agent group instead of creating a group.
The Agent Groups page appears.
The Create agent group screen appears.
The Create Agent Group: screen appears.
The Agent Group members screen appears.
The Create Agent Group screen reappears. The agent objects in the group appear in the Group Members list.
The agent group is created and a confirmation screen appears.
The SharePoint connection wizard requires an Agent Object that supports CA SiteMinder® 4.x functionality. Define this agent object on your Policy Servers.
Important: Do not add the 4.x agent object to any agent group, realm, or policy. This agent object exists only to support the internal operations of the Agent for SharePoint.
Follow these steps:
The Create Agent screen appears.
The Create Agent: screen appears.
The trust settings fields appear.
Specifies the IP Address of the Policy Server.
Specifies a password that is associated with the 4.x Agent object. The SharePoint Connection Wizard also requires this password.
Confirms a password that is associated with the 4.x Agent object. The SharePoint Connection Wizard also requires confirmation of this password.
The agent object is created and a confirmation screen appears.
An embedded Apache web server is part of the CA SiteMinder® Agent for SharePoint. An Agent Configuration Object (ACO) on the Policy Server contains configuration parameters that control the behavior of the agent running on the embedded web server.
Agents need values in certain parameters to start. For example, all agents need one value in either of the following parameters:
Other parameters control optional functions that you can set anytime. For example, if you decide to store agent logs on your web server, you can set those parameters later. Agents do not need values in logging parameters to start.
Follow these steps:
The Create Agent Configuration: Search pane opens.
Important! Only copy the SharePoint2010DefaultSettings ACO object. Do not copy any other object in the list.
Defines the identity of the web agent. This identity links the name and the IP address or FQDN of each web server instance hosting an Agent.
The value of the DefaultAgentName is used instead of the AgentName parameter if any of the following events occur:
Note: This parameter can have more than one value. Use the multivalue option when setting this parameter in an Agent Configuration Object. For local configuration files, add each value to a separate line in the file.
Default: No default
Limit: Multiple values are allowed.
Limits: Must contain 7-bit ASCII characters in the range of 32-127, and include one or more printable characters. Cannot contain the ampersand (&) and asterisk (*) characters. The value is not case-sensitive. For example, the names MyAgent and myagent are treated the same.
Example: myagent1,192.168.0.0 (IPV4)
Example: myagent2, 2001:DB8::/32 (IPV6)
Example: myagent,www.example.com
Defines a name that the agent uses to process requests. The value for DefaultAgentName is used for requests on an IP address or interface when no agent name value exists in the AgentName parameter.
If you are using virtual servers, you can set up your CA SiteMinder® environment quickly by using a DefaultAgentName. Using DefaultAgentName means that you do not need to define a separate agent for each virtual server.
Important! If you do not specify a value for the DefaultAgentName parameter, then the value of the AgentName parameter requires every agent identity in its list. Otherwise, the Policy Server cannot tie policies to the agent.
Default: No default.
Limit: Multiple values are allowed.
Limits: Must contain 7-bit ASCII characters in the range of 32-127, and include one or more printable characters. Cannot contain the ampersand (&) and asterisk (*) characters. The value is not case-sensitive. For example, the names MyAgent and myagent are treated the same.
Enables full log‑out and displays a confirmation page after users are successfully logged off. Configure this page so that it cannot be stored in a browser cache. If a cached page is used, session hijacking by unauthorized users is possible.
When the SharePoint users click the Sign out link, the following URI is used:
When the SharePoint users click the Sign in as another user link, the following URI is used:
If you have multiple SharePoint web sites below a top-level SharePoint website, add the URIs of the lower-level sites to the LogOffURI parameter.
Note: When the CookiePath parameter is set, the value of the LogOffUri parameter must point to the same cookie path. For example, if the value of your CookiePath parameter is set to example.com, then your LogOffUri must point to example.com/logoff.html
Default: /_layouts/SignOut.aspx, /_layouts/accessdenied.aspx?loginasanotheruser=true
Limits: Multiple URI values permitted. Do not use a fully qualified URL. Use a relative URI.
Example: (for a parent site of www.example.com with two lower-level sites named finance and hr respectively) /finance/_layouts/SignOut.aspx, finance/_layouts/accessdenied.aspx?loginasanotheruser=true /hr/_layouts/SignOut.aspx, /hr/_layouts/accessdenied.aspx?loginasanotheruser=true
The new values appear next to the parameters in the list.
The Create Agent Configuration Task is submitted for processing and the confirmation message appears.
The Policy Server communicates with a user directory to authenticate users. The user directory needs a connection defined in the CA SiteMinder® Administrative UI. Create a connection for your directory that contains users who require access to SharePoint resources.
Note: Only the directory vendors that CA SiteMinder® supports operate with the CA SiteMinder® Agent for SharePoint. For more information, see the Platform Support Matrix at www.support.ca.com.
Follow these steps:
The Create User Directory pane appears.
Note: The Require Credentials setting is required for LDAP directories which support anonymous search. This setting supports queries that the CA SiteMinder® Claims Provider makes to the user directory to support the SharePoint People Picker. For more information about these credentials, see the administrator of your directory server.
The Create User Directory task is submitted for processing, and the confirmation message appears.
Copyright © 2014 CA.
All rights reserved.
|
|