Skip to Content

attribute binding not checked


we have enterprise account and mapped LDAP account

We have define an user attribute. This work fine only on mapped account from AD. (attribute binding option 'import full name...' is cheked on LDAP authentication panel).

But when user is also 'enterprise', the additional user properties with our variable name is blank . After mapping these users have LDAP alias, but attribute binding option 'import full name...' under user properties is uncheck by default. How to check this by default ?




Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Dec 18, 2018 at 08:32 PM

    The is an account attribute that varies between an enterprise account and all the external directories (SAP, LDAP, AD) since enterprise does not import these values. In some cases that value can come into conflict with desired behavior but it's because a rule must be established when there are combined alias types.

    In the LDAP plugin is LDAP selected as the #1 under the attribute binding?

    If you go to the account properties of the dual aliased account is the import full name, email address, and other attributes still checked?

    Is the attribute you are having issues with the Full Name or something else?


    Add comment
    10|10000 characters needed characters exceeded