Symptoms

Implemented a custom K2SQL user manager using the following tutorial:

https://help.k2.com/kb001357

Now moving away from the K2SQL named user manager to another custom manager with a label of WL. The K2SQL user manager worked well however, with the following config file, whenever we log into runtime prefixing the username with "WL:", it still pickups the K2SQL context. I've even removed K2SQL altogether in the config and I'm experiencing the same issue. All Workspace and SMO user manager operations work with the WL label, just not runtime auth. Why is it still logging into runtime as K2SQL.

C:Program Files (x86)K2 blackpearlK2 smartforms RuntimeWeb.config












Please inform...
 

Diagnoses

N/A
 

Resolution

On the Manage Claims form (on K2 Designer site), select K2SQL and click edit. Then add the followings to the Security Label section:

Original Issuer set to FormsSTS
Claim Type set to http://schemas.K2.com/identity/claims/securitylabelname

Click OK to save the form. Restart k2 service, do an iisreset (on the server hosting smartform), refresh your browser. Then try to logon using your custom UM to resolve the issue.