Kerberos Delegation

Introduction

Kerberos will need to be configured if XLCubedWeb is installed on a different server to the underlying database and the Website is configured to use Windows Authentication.

If you have this type of setup and Kerberos isn't configured then you will receive a message such as "Server is unavailable" for Analysis Services or a "(null) user" error for SQL Server when trying to access published reports.

Most corporations have a standard setup for Kerberos and this would be handled by the Domain Administrators. The following is a guide to how to configure Kerberos in the simplest case but is no means a "Best practice" guide as each domain setup and infrastructure can vary enormously.

There are also many other factors that can impact a successful implementation Kerberos, such as network infrastructure, client security settings and software. The following guide will assume that all the clients will be running Internet Explorer and there is only one domain with everything located on the same physical network with no firewalls/routers that could filter Kerberos requests.

Information Required

Before configuring Kerberos you will need to know the following information:

What the networks domain name is - this is needed to get a server's Fully Qualifed Domain Name (FQDN): server.domain

The name and FQDN of the Web Server: Webserver The name and FQDN of the Analysis Services: AnalysisServices The name and FQDN of the SQL Server (if configuring SQL connections): SQLServer

The User ID for the XLCubed Application Pool configured for the XLCubedWeb website: WebUser The User ID the Analysis Services service is running as: ASUser The User ID the SQL Server service is running as: SQLUser

Access Required

You will need to be a Domain Administrator to perform any of the configuration steps