LDAP Custom Variables

You can alter the way Process Director interoperates with LDAP, defines LDAP users, authenticates with LDAP, and other functions by using the custom variables in this section.

Properties

Link

This a boolean value that determines whether "fast" LDAP authentication will be used. The default is False.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.fAuthFastLDAP = true;
}

Link

This a boolean value that determines whether LDAP authentication is enabled. The default is False.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.fAuthLDAP = false;
}

Link

This a boolean value that determines whether LDAP authentication using the extended LDAP API is enabled. The default is False.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.fAuthLDAPEx = false;
}

Link

This a boolean value that determines whether LDAP users will automatically be added as Process Director users after authentication. The default is False.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.fAuthLDAPAutoAdd = false;
}

Link

This a string value that contains the name of the LDAP field containing the GUID property of the user record. In Active Directory, this would be "displayName".

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.LDAP_DisplayName_Field = "Display Name";
}

Link

This a string value that contains the name of the LDAP field containing the user's email address. In Active Directory, this would be "mail".

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.LDAP_Email_Field = "mail";
}

Link

This a string value that contains the name of the LDAP field containing the GUID property of the user record. In Active Directory, this would be "objectGUID".

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.LDAP_GUID_Field = "ObjectGUID";
}

Link

When set to the default value of ReferralChasingOption.All, this variable tells the LDAP server to forward the authentication to all other servers. This is used when the LDAP server containing the user records is for a different domain than the domain against which you wish to authenticate.

The possible options for referral chasing are:

  • All: Chase referrals of either the subordinate or external type.
  • External: Chase external referrals.
  • None: Never chase the referred-to server. Setting this option prevents a client from contacting other servers in a referral process.
  • Subordinate: Chase only subordinate referrals which are a subordinate naming context in a directory tree. The ADSI LDAP provider always turns off this flag for paged searches.
Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.LDAPEx_ReferralChasing = ReferralChasingOption.All;
}

Link

This a integer value that enables you to set a custom page size for the LDAP records to be returned. The default value is 0. Be advised that setting this value may cause some LDAP servers to crash. The maximum page size recommended for Active Directory is 1000.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.LDAP_PageSize = 0;
}

Link

This a string value that contains the URL of the LDAP server.

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.LDAP_URL = "ldap://LdapServerName.com";
}

Link

This a string value that contains the name of the LDAP field containing the User ID. In Active Directory, this would be "sAMAccountName".

Example

public override void SetSystemVars(BPLogix.WorkflowDirector.SDK.bp bp)
{
    bp.Vars.LDAP_UserID_Field = "sAMAccountName";
}