For the Bind User, we use: *<domain>/<username>* For the User Search Filter, we use: *sAMAccountName=$\USER$* (this applies to AD LDAP only I think)
Also, did you complete the ARDBC LDAP Configuration form settings too? I don't remember if that was required but we have that set too. Regards, Michael Gould US House of Representatives On Thu, May 22, 2008 at 5:13 PM, Grooms, Frederick W < [EMAIL PROTECTED]> wrote: > ** I've seen cases where you need to use the testco\tuser1 format as well. > > Is the error in the log after the ldap_simple_bind for the tuser1 or after > the user you are trying to log in as? (You may need to set > Plugin-Log-Level:400 in your config to get the detail info). > > If it is after the user login attempt you may have your filter incorrect. > We use sAMAccountName=$\USER$ for the filter. > > > Fred > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *J.T. Shyman > *Sent:* Thursday, May 22, 2008 3:56 PM > > *To:* [email protected] > *Subject:* Re: ARS 7.1 Area LDAP config issue > > ** > > Kevin, > > > > Yes, the bind user should be in the same format as the User > Base. That is: CN=<user name>,OU=<container>,DC=<domain>,DC=<domain> > > > > Your AD admin, if that isn't yourself, should be able to give > you the distinguished name for the user. > > > > --- J.T. Shyman > > > ------------------------------ > > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Kevin Pulsen > *Sent:* Thursday, May 22, 2008 4:50 PM > *To:* [email protected] > *Subject:* Re: ARS 7.1 Area LDAP config issue > > > > ** > > Nope, that didn't work either > > tuser1 is the account I am attempting to read AD with > > testco.com is the domain > > and tuser1 is located in ou=Support Desk,ou=Admins,ou=NETWORKOPS. > > shouldn't it be something like cn=tuser1,ou,ou,dc ??? > > thanks Kevin P. > > > > > ** > You are perhaps typing the wrong bind user name or typing the wrong > password.. If it is really testco\NETWORKOPS\Admins\Support Desk\tuser1 try > \\testco\NETWORKOPS\Admins\Support Desk\tuser1. Maybe its missing the > double back slash in the beginning.. > Joe > > > ----- Original Message ---- > From: Kevin Pulsen <[EMAIL PROTECTED]> > To: [email protected] > Sent: Thursday, May 22, 2008 4:30:34 PM > Subject: ARS 7.1 Area LDAP config issue > > ** > Hello all, > > I'm trying to config the AREA LDAP form for Active Directory > authentication, when a user login into the Remedy client. > I have followed the documentation from the integrating 7.10 guide and have > the following values set in my AREA LDAP form - > > Host Name* - tcdc1.testco.com > > User Base* - dc=testco,dc=com > > Port Number - 389 > > User Search Filter* - cn=$\USER$ > > Bind User - testco\NETWORKOPS\Admins\Support Desk\tuser1 > > Group Membership - None > > Bind Password - ************* (no it's not really *'s) > > Use Secure Socket Layer - No > > Chase Referral - No > > I have the EA RPC set to 390695 and Authentication Chain Mode set to ARS > -AREA -OS > > When I attempt to login as a predefined user (with an existing Remedy ID > setup, no password) It fails and gives the following error in the > arplugin.log - > > <ARSYS.AREA.LDAP> <SEVERE> Bind: Invalid credentials (LDAPERR Code 49) > 80090308: LdapErr: > > What am I missing for the AREA LDAP config? > > Please help... > > Thanks.... Kevin P. > > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
