George, Well I feel stupid. I set the alias to sAMAccountName because I want the alias to be used for authentication. The working configuration is for the userID to be set to sAMAccountName and the alias left blank in the LDAP set up.
Thanks for your help! Kyle On Tue, Jun 14, 2011 at 12:51 PM, George Niculae <[email protected]> wrote: > On Tue, Jun 14, 2011 at 9:22 PM, George Niculae <[email protected]> wrote: >> On Tue, Jun 14, 2011 at 9:18 PM, Kyle Haefner >> <[email protected]> wrote: >>> George, >>> >>> openUC 4.4.0- 2011-06-07EDT05:00:13 ip-10-72-38-198 >>> >>> I updated today. What log shows LDAP authentication? >>> >> >> Check sipxconfig.log and see if any error there. Otherwise I suggest >> to take a pcap and see if AD rejects authentication >> >>> >>> ldap_attr_map_id | user_property | ldap_attr >>> ------------------+----------------------------------+---------------- >>> 3 | firstName | givenName >>> 3 | lastName | sn >>> 3 | userGroupName | ou >>> 3 | userName | sAMAccountName >>> 3 | createdAddressBookEntry.jobDept | department >>> 3 | imId | sAMAccountName >>> 3 | createdAddressBookEntry.jobTitle | title >>> 3 | emailAddress | mail >>> 3 | aliasesString | sAMAccountName >>> >> >> I'll map same attributes and give it a try, >> > > I'm not sure you can import users with this configuration - having > sAMAccountName for both user id and aliases will trigger exception on > user creation, can you double check your config? > > George > -- Kyle Haefner, M.S. Communication Systems Programmer Colorado State University Fort Collins, CO Phone: 970-491-1012 Email: [email protected] _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
