On Fri, Apr 16, 2010 at 05:17:58PM -0400, Andy Harrison wrote: > On Wed, Apr 14, 2010 at 12:13 AM, Lev Lafayette <[email protected]> wrote: > > > > We have our rt web interface behind https requiring authentication through > > LDAP. > > > > However we have certain queues that would like to provide outsiders (that > > is, people outside our LDAP) to connect to, preferably with a more limited > > interface. Their authentication could be through something like .htpassword > > > > Has anyone tried anything like this? > > If you're achieving your ldap auth via the apache module, it will be > more difficult. However, if you can use it, the > RT::Authen::ExternalAuth module will allow you to set up multiple > authentication sources. > > http://wiki.bestpractical.com/view/ExternalAuth > > I have it working using two ldap sources.
If you're using RT::Authen::ExternalAuth then you can just use internal RT accounts and the SelfService UI and configure your rights properly and you'll get the feature the original poster sounds like he was looking for. -kevin
pgpYT91irSmpL.pgp
Description: PGP signature
Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
