K2 SP2013 SmartObjects Performance Issues

Good day Decawi

Could you please see more about this issue and resolution here: https://help.k2.com/support-services/kbt140518.

Best,

Sunrise

Hi Decawi

The 'SharePoint Token Service' was re-added  to resolve the performance issue see information below:

1. To obtain the unique thumbprint for each SharePoint farm, please use the SharePoint Powershell command below:

(Get-SPServiceApplication -Name SecurityTokenServiceApplication).SigningCertificateThumbprint

2. Replace the thumbprint below with the thumbprint returned from the SharePoint Powershell and execute against K2 database (a database backup is recommended):

DECLARE @issuerId INT

INSERT INTO [K2].[Identity].[ClaimIssuer] (Name,Description, Issuer, Thumbprint, Uri, UseForLogin)

VALUES ('SharePoint Windows STS', 'SharePoint Windows Authentication', 'SharePoint', 'B2626522EB3B2871EDA28233B885390457BF8058',null, 0)

SET @issuerId = SCOPE_IDENTITY();

UPDATE [K2].[Identity].[ClaimTypeMapping]

SET IssuerID=@issuerId

WHERE ID=2

UPDATE [K2].[Identity].[ClaimTypeMap]

SET ClaimType = 'http://schemas.microsoft.com/sharepoint/2009/08/claims/userlogonname'

WHERE ID=3

INSERT INTO [K2].[Identity].[ClaimTypeMap] (ClaimTypeMappingID, ClaimMappingType, OriginalIssuer, ClaimType, ClaimValue)

VALUES (2,'IdentityProviderClaim', 'SecurityTokenService', 'http://schemas.microsoft.com/sharepoint/2009/08/claims/identityprovider', 'windows')

3. Restart the K2 blackpearl service

This is also possible using the K2 Management site as per:

http://help.k2.com/onlinehelp/k2blackpearl/icg/4.7/default.htm#tut/howto_spsts_sfmanagement.htm

Regards

Elvis

Good day Decawi,

It's possible that the upgrade has wiped out the 'SharePoint Token Service' issuer and mappings necessary for the SharePoint 2010 V2/legacy SmartObjects; which results in multiple retry attempts to get the claims username that had added to the overall execution time/performance issue.

With the information provided by "@ElvisJacob", I believe it would get resolved but you might consider logging a support ticket so that, a relevant support engineer is at hand to go through the process.

Kind regards,

Dumisani