Giving Workflow Management Permissions

Hi Nicolas,

When you refresh your worklist through workspace with the user from the other domain...is the correct user being authenticated in the server console? It possibly going through as ANON.

Hi Gert,

Yes, this is the correct user name (both in Worklist and in the workspace header where it says "logged in as ... ").

I'm asking this because the label that is shown at the top of the browser is not always correct and will almost never show you if the call is going through as anon. Would it be possible for you to mail me your k2server log? Note that you should have the logging level set to 'All'.

Thanx

What do you want me to do before sending the log, in order to "fill" it? Because, there is nothing for today, even with logging level set to "All" in the config file. I suppose giving permissions is not logged, is it?

Could you log into workspace and also try to deploy a process from studio from the other domain. Please for now keep the process basic with no sharepoint/IP integration. That should give a pretty detailed log.

Please ensure that you enable FileExtension logging in HostServerLogging.config and setting the level to All.

 Thanx

Ok, FileExtension logging was disabled... Now I have a real log file.

I logged into the workspace with my original domain account, then with my second domain account, and I have finally deployed a basic process with this second domain account.

Edit: log sent. Thank you very much Gert.

Could you please attach the log file to the thread or mail it to me at gert@k2.com.

Done!

(Yes, it's deploying now, with a basic process. As stated in the other thread http://k2underground.com/forums/thread/20260.aspx dedicated to this particular issue [sorry for mixing problems], I suppose it has something to do with Sharepoint Integration. Nevertheless, I still cannot accede the workspace with full permissions)

Oh, I forgot to say this, but for a user which is in the "primary"/original domain, I get the "Management" tab in the workspace as soon as I give them the corresponding right. The problem occurs only for users in the domains I manually added to the K2 security label.

OK,

Here’s what you need to do :

·         Open your WorkSpace’s web.config file. Default location is “blackpearl installation dirworkspacesite”

·         Add a new AD Connection String in the connection strings section. E.g.    <add name="ADConnectionString2" connectionString="LDAP://Domain2.com" />

·         In the Membership/Providers section add a new provider pointing to the newly added connection string. Note that the name should be different from the existing one.

E.g.        <add connectionStringName="ADConnectionString2" connectionProtection="Secure" enablePasswordReset="false" enableSearchMethods="true" requiresQuestionAndAnswer="false" applicationName="/" description="Default AD connection" requiresUniqueEmail="false" clientSearchTimeout="30" serverSearchTimeout="30" attributeMapUsername="sAMAccountName" name="AspNetActiveDirectoryMembershipProvider_Domain2" type="System.Web.Security.ActiveDirectoryMembershipProvider,System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />

·         Now save -> close and open up workspace.

HTH

Gert

I confirm it works. Thanx!

Now, one last problem : I can't deploy a "Sharepoint Events Process" workflow with a user from the added domains, nor start such a process (when it has been deployed with the K2 admin account). New thread!