Hello everybody and thanks for your suggestions, The actual problem was that i was using to authenificate against RT normal user format from Active Directory, and Request Tracker ask for the pre-Windows 2000 username format, and in my situation the two are different. The problems is solved. Anyway is there a possibility to force RT to use the normal user format?
Many Thanks, On Tue, Aug 21, 2012 at 5:34 PM, Joachim Thuau <[email protected]> wrote: > It searches from the base down (subtree). Sadly, it looks like his "base" > are not under a single container. (limit less, correct me if I > misunderstood). > > You might be able to defined more auth services, each one identical, > except with different bases, to auth against. > > Thanks, > Jok > -- > | Joachim Thuau | IT Systems Engineer - Linux / SpaceX | > > > On 8/21/12 8:11 AM, "Thomas Sibley" <[email protected]> wrote: > > >On 08/21/2012 05:58 AM, Limit Less wrote: > >> I have set up a new Request Tracker server, that uses > >> the RT::Authen::*ExternalAuth *extension. > >> Everything is working fine, and i am able to authenticate users account > >> from the Active Directory into RT, the problem is that i have is that my > >> organisation has a complicated structure, with many OU, and the ldap > >> search for users from what i could figure it out is made having as a > >> scope just one level, what would i need is to have as a scope a whole > >> Subtree. > > > >The whole subtree is searched. Here's the line of code: > > > > > https://github.com/bestpractical/rt-authen-externalauth/blob/master/lib/RT > >/Authen/ExternalAuth/LDAP.pm#L57 > > > >and the documentation for the default it's relying on: > > > >https://metacpan.org/module/Net::LDAP#search-OPTIONS- > > > >You should post your entire config, and error messages, etc. > >
