On Fri, Oct 21, 2011 at 12:16 PM, Kalimuthu Samayan
wrote:
> but I am failing to have additional features listed below to authentication
> like,
>
> -Search and Bind a user in LDAP by passing Group ID who can authorise any
> specific user belongs to the group
Look here for group-based authorizati
I did this using a directive--you can put your LDAP auth stuff
there and apply it to the top-level file system directory of your application.
Users won't be able to bypass that. (I'm assuming that you're currently using a
directive and that your entire application lives in a single
directory
Thanks Mark!
On Wed, Oct 5, 2011 at 5:01 PM, Mark Montague wrote:
> On October 5, 2011 17:44 , Thomas Smith wrote:
>>
>> Can someone help me get my desired configuration to work?
>
> Maybe someone who is not me can :) I'd be able to help you better if you
>
alid-user
>
>
>Order deny,allow
>Deny from all
>SetEnvIf Request_URI "^/(NoAuth|REST/1.0/NoAuth)(.*)$" allow
> Allow from env=allow
>Satisfy Any
>Options +ExecCGI
Hi,
I'm configuring the Request Tracker to use Apache authentication. I've
had RT running for quite a few years, but (up to this point) only
using its internal database for authentication.
Software:
* CentOS 4.8
* Apache 2.0.63
* RT 4.0.2
* mod_fastcgi 2.4.6
I created a Directory directive for /