manual

25 www.microsoft.com/sharepoint
Push-down content type publishing updates from the content type gallery to
subsites and lists by using the content type Whether to update existing instances of
the changed content types in subsites and libraries.
Example Scenario
Consider a company that has four departments: IT, HR, Products, and Legal. IT, HR, and
Legal each have their own site collection that serves as each department’s portal, while
there are several product team site collections, one for each product team. All these site
collections are contained in the same Web application. Two governance requirements
have been specified for managing metadata: All documents that are created must
include a core set of properties, and all keywords must be stored centrally.
To meet the first requirement, IT creates a content type called Document-Base at the
root site collection of its department portal. IT adds columns to Document-Base for all
of the required properties. Then IT creates a managed metadata service application and
specifies the root site collection as the hub of the content types it is sharing. IT publishes
the service and provides the service’s URL to all departments. A connection to IT’s
managed metadata service is created. The second requirement — that all keywords be
stored centrally — can be satisfied when each site collection connects to the service hub
by specifying that managed metadata service as the default keyword store.
This scenario illustrates how the metadata service can be configured so that all
departments have access to a centrally managed set of metadata defined in the
Document-Base content type, and all keywords can be centrally managed and stored in
a single location (IT’s term store), so all departments can use all of the keywords.
Claims-based Authentication
SharePoint Server 2010 incorporates a new, more powerful and flexible authentication
model that works with any corporate identity system, including Active Directory®
directory services, LDAP-based directories, application-specific databases, and new user-
centric identity models such as LiveID. This model uses claims-based authentication and
a new product, code-named “Geneva.” Claims-based authentication is built around the
concept of an identity and is based on standards — WS-Federation, WS-Trust — and
protocols like the Security Assertion Markup Language (SAML). An identity is a set of
information about a user, such as name, e-mail address, department, and so on.
“Geneva” is actually three related technologies: Active Directory Federation Services
(formerly known as Geneva Server), Windows Cardspace™ (formerly known as