Dynamic Active Directory Service

After digging into the code a little bit. Active Directory will put a limit of 1000 records on a search that does not have the PageSize declared. I added this line of code to: ADHelper.cs in the ActiveDirectoryDynamicSO project The Code I added:

public Exception getUsers(ref ServiceObject so)
        {
            Exception exc = null;
            try
            {
                //Need to decide if will allow user to pass domain in as a parameter?
                string conString = getLDAPPath("");
                //DirectoryEntry dirEntry = new DirectoryEntry(conString);
                DirectoryEntry dirEntry = getDirectoryEntry(conString);
                DirectorySearcher dSearcher = new DirectorySearcher(dirEntry);
                //Set the filter for the search
                dSearcher.Filter = getADUserLookUpString(ref so);
                int limit = 2000;
                if (so.Properties["MaxSearchResultSize"].Value != null)
                {
                    if (so.Properties["MaxSearchResultSize"].Value.ToString() != "*")
                    {
                        int.TryParse(so.Properties["MaxSearchResultSize"].Value.ToString(), out limit);
                    }
                }

                Method meth = so.Methods[0];
                dSearcher.PageSize = 1200;
                dSearcher.SizeLimit = limit;
                System.DirectoryServices.SearchResultCollection sResults = dSearcher.FindAll();
                so.Properties.InitResultTable();
                foreach (SearchResult sResult in sResults)
                {
                    addReturnPropFromDirObject(ref dirEntry, ref so,sResult);
                    SetTransactionSuccessful(ref so);
                    so.Properties.BindPropertiesToResultTable();
                }
                dirEntry.Close();
            }
            catch (Exception ex)
            {
                exc = ex;
            }
            return exc;
        }

Recompile, move K2.PSUK.ActiveDirectoryDynamicSO.dll to the ServiceBroker directory on the K2 server, refresh Service Object, Refresh Service Instance, and rerun the SmartObject.  This did the trick!

After carefully followed the instructions from the document provided as part of the downloaded zipped.

From SmartObjects - Services - Test tool, as a test I tried to execute "GetUsers" and "ReadUser" but received an error message as:

"Index was out of rang. Must be non-negative and less than the size of the collection.

Parameter name: index

Service: DynamicADSO

Service Guid: [guid info]

Serverity: Error

has anyone experienced this error or could you please kindly provide some advices how I can resolve this error.

thanks

Hello everyone,

Share your ideas and thoughts to me please, I have following condition:

Source code changes:

1. GetUsers method - increased size limit

2. Modified SchemaObject.xml - Added input and output attributes (including standard, custom)

Steps:

1. ServiceType registered 

2. ServiceInstance created

3. SmartObjects generated

4. When execute SmartObject method from SmartObjects - Services - Tester.exe

Error thrown with: The user name or password is incorrect.

We have normally running K2 environment, standard AD Service2 is working fine.

Methods from 1-4 all executed through the main service account configured for K2 environment.

Main service account can query normally from the ActiveDirectory using Powershell script.

Thanks in advance.

Was there ever a resolution to the port from Andrew Blinco above?

We are encountering a similar issue with the installation on our validation/test environment.  We have installed the Dynamic ADSO the same way on our development environment with out any issues and files are installed in the smae locations/directory paths on both environments.

Thank you

Jason Milks

this is a really useful service.  I did however encounter performance issues when running the GetUsers method when returning 600+ users.  It was taking over 60 seconds whereas the ADUser2 service was taking under 1 second to return the same number of users.

to resolve this problem i added a new function to the code to set the Searcher.PropertiesToLoad property to only the items being returned.  this reduced the time from over 60 seconds to sub 1 second.

dSearcher.Filter = getADUserLookUpString(ref so);

dSearcher.PropertiesToLoad.AddRange(getReturnPropsFromServiceObject(ref so));

where getReturnPropsFromServiceObject is:

private string[] getReturnPropsFromServiceObject(ref ServiceObject so)

{

List<string> returnProps = new List<string>();

Method meth = so.Methods[0];

for (int c = 0; c < meth.ReturnProperties.Count; c += 1)

{

Property prop = so.Properties[meth.ReturnProperties];

if (prop.Name.IndexOf("UAC_") != -1)

{

if (returnProps.IndexOf("userAccountControl") == -1)

{

returnProps.Add("userAccountControl");

}

}

if (prop.Name.IndexOf("OrganisationalUnit") != -1)

{

returnProps.Add("DistinguishedName");

}

else

{

returnProps.Add(prop.Name);

}

}

return returnProps.ToArray();

}

we have a problem where if we look for multiple people via a property

for people that have blank properties, they are getting populated from the person above them

for example - the property securityLicence is used by 3 people, yet when searching for users with the result we are getting others populated

Hello,

does this service work on K2 FIVE ? 

I get this error when i want to register the service type from the smartobject tester ++: 

Regards,

Kévin

In case of the "The user name or password is incorrect" try to change service instance to use Impersonation instead of Service Account. It helped in my case.

Hi

if we have load balancer setup, do we have to add this in both server?

Thanks