Add Network (AD) Users Programmatically?

[PeterB]

As there's no native support for AD Group (authorization) in CheckBox yet as per this post I am attempting to sync an AD group with a CheckBox group.

However, it seems you have to add the network user first before you can add them with a CheckBox group. This is proving difficult: I can add a normal (non-network) user, but cannot work out how to programmatically add a network user (e.g. specify domain) via the Web Service API. That is, the _userManagementProxy.CreateUser() doesn't seem to have a domain parameter (overload).

How can I associate network (AD) users with CheckBox groups?

[N.B. I did attempt to associate the AD user with the CheckBox group directly without associating the user with CheckBox, but this didn't seem to work].

Thanks.

[pwiesner]

I reviewed the user management web service and you are correct, it does not look like you can create a network user. I am not entirely sure why this is not possible and I have opened a development tracker item for this issue.

In order to create network users today you will need to use the Direct API.

///

/// Create a user and return an identity for it.
///

/// UserName of the user to create.
/// Created user's password.
/// Domain of the created user.
/// Status message for the operation.
/// User Identity
/// User Management
public static IIdentity CreateUser(string name, string password, string domain, out string status) {...}

Please let me know if you have any additional questions about the Direct API

Note: It looks like the forum is stripping the xml from the documentation.

[PeterB]

Thanks for the reply,

I can get the Direct API working with my ASP.NET Web Application (by including the APITokenCacheProvider files and tweeking the Security.xml file), however is there a better to use it for ASP.NET apps? For example, we're not really comfortable with all these XML configuration files with fully qualified paths to files (and the production deployment implications of this).

Perhaps there's a way to use relative paths to these files?

Thanks again.


-----
P.S. for any getting this error:

{"Method 'DoRemove' in type 'Checkbox.Web.Caching.AspNetSessionBackingStore' from assembly 'Checkbox.Web, Version=4.3.0.33, Culture=neutral, PublicKeyToken=null' does not have an implementation.":"Checkbox.Web.Caching.AspNetSessionBackingStore"}

Check that you have the latest 'Checkbox.Web.dll' file, the one in the CheckBoxAPITest folder is out of date, but the one in the '\Samples\CustomItem\SelectManyDependentSelect1\Re ferences' works.

[pwiesner]

Unfortunately the configuration files used by the Direct API require fully qualified paths.

I have escalated the priority of this issue. The user management web service will be updated to include a method for creating network users in the next release of the product. Checkbox 4.6 is currently beginning QA and we hope to have it released in the next few weeks.

[pwiesner]

Checkbox 4.6 will include methods for creating a network user and to change an existing network user's domain.

[PeterB]

Thanks again,

As per our support ticket - we look forward to the new version, and will likely persevere with the Direct API in the meantime.

Incidentally, is there any update on the support for AD Groups (authorization) as per the link at the start of the post?

Cheers.