I forgot to thanks folks and close up this thread with the resolution, so here it is.
I added this section to my RT_SiteConfig.pm # Enable ApacheLDAPAuth Set($WebExternalAuth, 1); Set($WebFallbackToInternalAuth, true); Set($WebExternalAuto, 1); That was it. Since Apache was already working with my AD via: http://www.turnpike420.net/linux/Apache_ADS_AuthLDAP.txt (This was applied to the Directory for RT inside the virtualhost in the conf.d/rt.conf file.) All I had to do was add the above and create the RT user for each person I wanted to allow in, password in RT is completely overlooked as this solution presumes if you auth'd in the browser, your username must be you, so if that username is in RT, then you can be that person and use RT. :) Anyway, thanks to those who helped! David McD On 2/9/06, Lance A. Brown <[EMAIL PROTECTED]> wrote: > Michael Alan Dorman wrote: > > "Lance A. Brown" <[EMAIL PROTECTED]> writes: > > > >>Check the documentation and RT wiki. RT is quite fliexible in handling > >>users and you may be able to wedge in your LDAP userbase using a perl > >>module or via an htaccess-style authentication request. > > > > > > You can authenticate via LDAP very easily, but you still have to > > create the accounts within RT in order for them to be granted rights. > > True, but that could be scripted. > > --[Lance] > > -- > Celebrate The Circle http://www.celebratethecircle.org/ > Carolina Spirit Quest http://www.carolinaspiritquest.org/ > My LiveJournal http://www.livejournal.com/users/labrown/ > GPG Fingerprint: 409B A409 A38D 92BF 15D9 6EEE 9A82 F2AC 69AC 07B9 > CACert.org Assurer > -- > TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug > TriLUG Organizational FAQ : http://trilug.org/faq/ > TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ > -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
