Create user/Delete user/Create User issue

Originally Posted by pwiesner

I would suggest using the GetUserIdentities method to determine if a user already exists. You will want to search on the UniqueIdentifier field and use the username as the search value.

string[] userIdentities = wsProxy.GetUserIdentities(contextToken, "UniqueIdentifier", userName);

I have implemented this method but still encounter the same issue. I can correctly identify if a user ID exists using the GetUserIdentities() method, but when I call CreateUser(), the method either:

1. Returns an error is the updateIfExists parameter is false.
2. Returns successfully to the custom app if updateIfExists parameter is true, but the user ID is not added to the table ckbx_Credential. However, in this scenario, the profile data in the table ckbx_CustomUserFieldMap does get updated.

So, currently, I am unable to use the web service to recreate a deleted user.

[ncushing]

I'll take a look at the code behind the scenes to see what is going on. The software should be checking the credential table. It's possible that the identity isn't being cleared from the identity cache when the user is deleted and that is what is causing the confusion. In any case, I'll take a look and get back to you to see how we can get you past this issue.

-Noah

Noah,

I would agree with your thoughts. If I delete the user, reset IIS, and then recreate the user through the web service, the user is created.

It should be noted that the recreate problem occurs - when not resetting IIS - both when I delete the user from the Checkbox UI and the web service API. The difference in behavior is in which method I use to recreate the user: the Checkbox UI successfully creates the user (seemingly regardless of what's in cache) while the web service API does not create the user.

[ncushing]

Thanks for the additional information. I'll take a look at the source to see if I can figure out why the re-create works in one instance and not the other.

-Noah

Do you have any additional information on this? I'm able to work around this issue, but it makes testing our custom application a bit tedious. An estimation of when this might be fixed would be helpful.

[ncushing]

I'm still looking into the issue, but I expect that we'll have it fixed for the 4.5 release, which is currently undergoing internal QA evaluation.

Great! Thanks for the update.