Ever Wondered How Developers are Authenticated in K2 Designer?

I hadn’t. Not really. Until today.

I’ve a client who’s forcing me to learn — my main contact isn’t familiar at all with K2, so I’m getting asked lots of questions. Today, he wanted to give a person access to the K2 Designer. I had no idea how to do it, but I offered to dig into the server’s configuration files to figure it out.

Here’s what I found.

There is a Web.Config file in the server’s {drive}:\Program Files (x86)\K2 blackpearl\K2 smartforms Designer directory. In under the <system.webServer> /<security> node is a node called <authentication>. The node should resemble this:

  <remove users="*" roles="" verbs="" />
  <add accessType="Allow" users="domain\user1,...domain\user3" />

I’m used to configurations that set the user as an Active Directory group,
such that membership is changed through AD, without messing with the Web.Config.
However, this organization is assigning AD Usernames directly.

If you find the need to give a new developer access to K2 Designer, check this file to figure out how that’s done. If an AD group appears in the users attribute, your best bet may be to ask an administrator to include the new person in that group. If individual accounts are listed (as in the above example), seek an administrator with the ability to edit the files in that directory. (If that sounds odd to you, note that many organizations won’t allow contractors that level of file system access.)