Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 10 replies
  • Subscribers 5 subscribers
  • Views 26881 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

username variable on activesync profile does not work

WSBD

I recently installed version 3.5.0.4 for the windows 8 support, and I have problems with deploying activesync profiles on both Android and IOS. The username variable doesn't work.  I use the variable %_USERNAME_% and %_EMAILADDRESS_% on both the username and email address field.

In customer configuration I have set up an external directory. (ActiveDirectory LDAP) I am using the following LDAP fields : fo rr username : samAccountName

and emailaddress : mail

After installation I see on the device the email address is correctly translated but the username field stays blank. Also you are unable to change the settings on the device since the field is grayed out.


Before I used version 3.0.2 and had no problems with the username variable. Any ideas, maybe it's a bug?

:42632


This thread was automatically locked due to age.
Parents
  • 0

    Hi WSBD,

    thanks for your provided information.
    It seems as if you have entered the samaccount name manually when configuring the LDAP connection for the customer in questions. Unfortunately, this is case sensitive. The field 'samaccountname'.does not exist in the LDAP directory while the field 'sAMAccountName' does. I don't know right now, why the login at the SSP works without any problems.

    To solve this, I would like to ask you to log in as a super administrator in your SMC console.

    Edit the customer in question and press the 'Configure external directroy' button.

    During the step 'Search fields' make sure to choose the 'sAMAccountName' from the drop down box.

    Finish the directory configuration and try the deployment of the profile with the variable again.
    This time the profile should be deployed correctly.

    I will verify with our development team why this issue occurs and why the login at the SSP just works fine.

    Best regards

    Stefan

    :42756
Reply
  • 0

    Hi WSBD,

    thanks for your provided information.
    It seems as if you have entered the samaccount name manually when configuring the LDAP connection for the customer in questions. Unfortunately, this is case sensitive. The field 'samaccountname'.does not exist in the LDAP directory while the field 'sAMAccountName' does. I don't know right now, why the login at the SSP works without any problems.

    To solve this, I would like to ask you to log in as a super administrator in your SMC console.

    Edit the customer in question and press the 'Configure external directroy' button.

    During the step 'Search fields' make sure to choose the 'sAMAccountName' from the drop down box.

    Finish the directory configuration and try the deployment of the profile with the variable again.
    This time the profile should be deployed correctly.

    I will verify with our development team why this issue occurs and why the login at the SSP just works fine.

    Best regards

    Stefan

    :42756
Children
No Data
Unfiltered HTML