SharePoint 2010 Cross-Farm Services And External Data Sources

There are several steps involved in the process of deploying cross farm services. Each step is very important to gain the overall results you are after.

Configuration of trusted farms ensures all of the farms that use exchanges can trust each other. Certificates have to be exported to a file. Make sure you back up that file before you connect to any of the cross farm services. Publishing service applications must be done before you will be able to successfully share it across farms. Connecting cross farm service applications provides a connection must be made to a service that is published by a remote farm. This will require the URL to be entered of the published service. This is going to be displayed when you publish it. The connection on the local farm has to be created so that it can be connected successfully to a service application for a remote farm.

Should there be two domains where the server farms are located, the User profile service application will require both of them to trust each other. With the Business Data Connectivity and Secure Store Service the domain of the publishing farm has to trust that of the consuming farm. None of the cross farm service applications are going to work if there isn’t a trust requirement in place for the two domains.

It is possible for certain service applications to access external data sources. This occurs through the access of a delegated Windows identity that will place some additional requirements on a given environment. These types of service applications have to be in the same domain as the SharePoint Server 2010 farm. This is where the service applications are housed. The other option is for the service application to be configured using the Secure Store Service.There are plenty of different service applications that can be found across the external data. They use a delegated Window identity. This includes:

  • Excel Services
  • InfoPath Forms Services
  • PerformancePoint Services
  • Visio Services

The service applications used to access external data sources must have a delegated Windows identity. Otherwise it has to be configured for the use of the Secure Store Service. This will store and maintain the credentials of a user or a service. When service applications are used to store credentials, they have to be authenticated before the data can be accessed.

If the external data sources aren’t within the same domain then authentication for the external data sources will fail unless you use the Secure Store Service. Farm servers can be split between two different domains but the application servers have to be found in the same domain as the external data sources.

There are several service applications and products that don’t have those requirements. They include:

  • Access Services
  • Business Data connectivity Services
  • Microsoft Business Connectivity Services
  • Microsoft Project Server 2010
  • Microsoft SQL Server PowerPivot for Microsoft SharePoint
  • Microsoft SQL Server Reporting Services

PerformancePoint Security Best Practices In SharePoint 2010 Authentication, Trusted Locations

Data content libraries that are trusted with SharePoint Server 2010 use document libraries that contain the PerformancePoint Services data connections. The .PPSDC files are used to manage connections for data sources. This includes Excel Services spreadsheets, OLAP Cubes, Relational databases, and SQL Server databases. The data sources in the Dashboard Designer are defined and stored in a trusted data connection library that SharePoint Server 2010 offers. The trusted data connection library consists of safe documents that belong to that particular library. Users are restricted when it comes to how data source files can be used. They can be read but not modified or deleted. Through PerformancePoint Services a document library is created through a default setting. Administrators do have the ability to manage those data connections on the server. This is accomplished through creating additional data connection libraries. When a user updates data source connections in a document library the information will be shared and updated through Dashboard Designer. There are many trusted lists that can be developed in a trusted SharePoint Server 2010 list. The list or the parent of a list allows the site collection to be trusted during the initial configuration. It can also be done later on through the Central Administrator. These lists include:

  • Filters
  • KPI’s
  • Reports
  • Scorecards

With PerformancePoint Services, the security setting for data sources gets stored in each of them. There is a setting that is used to determine if the server is connected with an unattended user account, a customized unattended user account, or an authenticated user. With the SharePoint Server 2010 Secure Store Service (SSS), the ability to securely store data is available. This includes the credentials that are associated with a specific identity or group. The Secure Store Service is available for all of the farms on SharePoint Server 2010. Each of the data sources is configured for a given user to work with the authenticated user credentials. This is referred to as the Unattended Service Account. This is a domain set of credentials that are duplication when a user is connecting to a data source.

The Unattended Service Account is used to manage the data source for the queries. This is done to prevent the PerformancePoint Services from accessing the content database when the query is being executed. With PerformancePoint Services, data is stored and retrieved through Unattended Service Account credentials. This takes place in the Secure Store Service verifications. The server has to keep both the user name and the password of a user so that they can access it. The user name is stored in the PerformancePoint Services and the password is stored in the Secure Store Service. It is important when you create an Unattended Service Account that you make sure it has the right access. There are data sources that that to be in place for it to function properly. Unattended Service Account credentials aren’t cached on a global scale. Instead, they get retrieved from the Secure Store Service as they are needed. When you open a WorkSpace file in Dashboard Designer, the credentials will be cached for the connection. The Unattended Service Account password is retrieved from the Secure Store Service so that it can be the target data source.

With claims based authentication taking place in the SharePoint Server 2010, there is support for many providers. It is used to communicate from the application servers and the front end web servers. PerformancePoint Services allows for the authentication of providers at the same time on one web application. This is limited though to when the Dashboard is used through a web browser. The Dashboard Designer relies on the web application to be extended. It is then configured in order to support the Windows authentication provider.


PerformancePoint Security Best Practices In SharePoint 2010 – A Primer

With PerformancePoint Services offered by Microsoft SharePoint Server 2010, the objects that get stored in lists and document libraries can be secure when used within a dashboarding / graphical application. This is accomplished by coupling through the Microsoft SharePoint Sever 2010 security model. There are additional products features that can be accessed for customizing that security. PerformancePoint Services are dependent upon the SharePoint Server 201 security model. However, there are special security considerations that need to be evaluated during the planning stages. That should also include how managing that security will take place. All of the security is managed within the SharePoint Sever Central Administration Website. This covers all of the shared resources as well as the user access.

You will find three different methods for source data Authentication with PerformancePoint Services. Custom Data allows for SQL Service Analysis Services to be able to authenticate a user through custom specs. The name of the user is considered a parameter of the custom data field for the connection string. The custom data option is only used for Analysis Service Data. It can be used with both the 2006 and 2008 servers. With Per User Identity authentication each of the users has individual accounts that are used to access all of the data sources. The use of Kerberos Delegation has to be incorporated. There is a domain administrator that configures the Kerberos Delegation between PerformancePoint Services and the data sources. The external data sources have to be within the same domain as the SharePoint Server 2010 farm or a failure will occur. Unattended Service Account are a shared user account that is used for access to all of the different data sources. This type of domain account is low privilege. It is stored in the Secure Store Service. In order to create an unattended service account, there has to be the proper access to the data sources. This is a requirement of the dashboard.

With PerformancePoint Services the data source connections are contained. This occurs with the data content and document libraries that are part of the document lists. The security of the content ensures that users aren’t able to run queries against those data resources when the query objects can’t be trusted. Therefore trusted locations within those libraries and lists are created. The Farm Administrator is able to set all of the locations for the farm to be trusted. They can also choose to identify specific locations to be trusted. The ability to define the locations in the farm that will be secure means that there is a great deal of flexibility. A Farm Administrator no longer has the responsibility of securing the entire farm when it isn’t absolutely necessary to do so. These trusted locations are able to offer additional layers of security. There are restrictions for the query to be executed in regards to various data sources and objects. The document library for a web application can be defined as being trusted. With PerformancePoint Services the configuration of trusted locations and settings are managed through the Central Administrator. The configuration can also be managed through the use of Microsoft PowerShell 2.0. When you are planning the security for PerformancePoint Services, you will need to decide if you want to secure your entire web application or only portions of it. There are often many locations found within a given farm that will be marked as trusted. They use the following hierarchy within the SharePoint Server for the data and data sources:

  • The use of trusted locations are disabled for various locations with data sources or content for the entire farm.
  • The web application contains trust lists and document libraries.
  • There is a collection site for the trust lists and document libraries.
  • Trust lists and document libraries placed in a site.
  • The farm has a trust list or document library in place.

The server will check if trusted locations are enabled when it is doing verifications. When it is enabled the server will check a list of trusted locations at the site collection. It will also look down the hierarchy to verify that all of the content is trusted. When items don’t use a data source they don’t have to be in a trusted location to be accessed. This includes KPI’s, dashboards, icons, and web pages. Trusted data source locations can’t be defined on a list or as a document library.