I have a directory that I want to protect access to.
For my local staff, I want that protection to be by CoSign.
For non-local staff, I want that protection to be by standard Apache BASIC
authentication using
AuthType Basic
AuthName "Restricted Files"
On October 16, 2011 19:17 , J LANCE WILKINSON wrote:
> I have a directory that I want to protect access to.
>
> For my local staff, I want that protection to be by CoSign.
>
> For non-local staff, I want that protection to be by standard Apache BASIC
> authentication using
>
> AuthTy
On 18 Oct 2011, at 10:46, Mark Montague wrote:
> http://www.electricmonk.nl/log/2008/10/24/apache-22-multiple-authentication-providers/
That's super interesting (at least to me), but I doubt very much that cosign is
close to "just working" with a AuthBasicProvider mechanism -- cosign isn't a
bac
On 18 Oct 2011, at 10:46, Mark Montague wrote:
> http://www.electricmonk.nl/log/2008/10/24/apache-22-multiple-authentication-providers/
That's super interesting (at least to me), but I doubt very much that cosign is
close to "just working" with a AuthBasicProvider mechanism -- cosign isn't a
bac
Mark Montague wrote:
> On October 16, 2011 19:17 , J LANCE WILKINSON wrote:
>> I have a directory that I want to protect access to.
>>
>> For my local staff, I want that protection to be by CoSign.
>>
>> For non-local staff, I want that protection to be by standard Apache
>> BASIC
>> authenticati
On October 24, 2011 11:33 , "J.Lance Wilkinson" wrote:
> They (those who run the CoSign installation for the institution)
> don't offer cosign/Friend here. I have no control over what
> kind of CoSign services are offered except my own services.
> They (as defined earlier) do offe
