Collapse All Expand All

K2 Workspace Service Account

In a distributed environment where components are installed on more than one server or if host headers are used, Kerberos security must be configured. One of the components of Kerberos is the Service Principal Name (SPN). Whenever user credentials must be passed from one system to another, the system that is attempting to pass the credentials must be trusted for delegation. For this step to take place successfully, Kerberos delegation must be configured.

Set SPNs

In order to access the K2 Workspace from another machine, you need to set the SPNs for the K2 Workspace Service Account.

The following placeholders are used in the commands:

• domain\K2 Workspace Service Account - The K2 Workspace Service Account that runs the K2 blackpearl application pool
• MachineName - The name of the computer on which the K2 Workspace is running
• MachineName.FQDN - The fully qualified domain name of the computer on which the K2 Workspace is running

Be sure to set all the SPNs as listed below. Also, the service account is required so be sure to specify the account properly.

If you have the K2 Workspace running on a cluster, be sure to use the name of the cluster and the fully qualified cluster name instead of a single node's machine name.

If you are using Host Headers to access your K2 Workspace, use the HostHeader value instead of the MachineName in the below commands. An SPN for each Host Header will need to be created.

Open a command prompt on a server that has the Windows Support Tools installed, and execute the following commands:

• setspn -A HTTP/MachineName domain\K2 Workspace Service Account
• setspn -A HTTP/MachineName.FQDN domain\K2 Workspace Service Account

After the commands have successfully executed, you can verify the SPNs were set by executing the following command:

• setspn -L domain\K2 Workspace Service Account

Configure for Delegation

After the SPN has been set, a new Delegation tab is available in Active Directory Users and Computers for the Service Account. By default, the option selected is the Do not trust this user for delegation. You need to set the account to be trusted for delegation, by following the below steps:

If you are running your Active Directory domain in Windows 2000 native mode, the Delegation tab will not be present. Instead, on the Account tab, you will see a Trust this user for delegation check box.

	Open Active Directory Users and Computers (Start > All Programs > Administrative Tools > Active Directory Users and Computers)
	Find the domain\K2 Workspace Service Account and view its properties
	On the Delegation tab, select the Trust this user for delegation to specified services only option
	Select the Use Kerberos only option, and click on Add
	Click on Users or Computers and select the domain\K2 Service Account you created as the K2 Server Service Account
	In the Available Services section, select both the K2HostServer and K2Server items listed:
	Click OK. Your properties should resemble the following:
	Click OK. This will allow the K2 Workspace Service Account to delegate to the K2 Server Service Account. Also, since the SQL Reporting Services reports will also be rendered in the K2 Workspace, the K2 Workspace Service Account should also be allowed to delegate to the SQLRS Account.
	Click Add again
	Click on Users or Computers and select the domain\Reporting Services Service Account you created as the SQL Reporting Services Service Account
	In the Available Services section, select the HTTP item listed:
	Click OK. Your properties should now resemble the following:
	If you are using SharePoint Integrated process, K2 Workspace Service Account should also be allowed to delegate to the MOSS Account
	Click Add again
	Click on Users or Computers and select the domain\MOSS Account you created as the MOSS Server Account
	In the Available Services section, select the HTTP item listed
	Click OK

 

 

---

K2 blackpearl Product Documentation: Installation and Configuration Guide 4.6.10