Re: [Cosign-discuss] This friggin' sucks....

2009-03-06 Thread Trek Glowacki
On Mar 4, 2009, at 6:08 AM, Peter Schober wrote: > * Trek Glowacki [2009-03-03 21:24]: >> So, to a third party observer both versions of the Cosign Equation >> evaluate to "no value".Not knowing the exact parameters of the >> Equation he can only assume one of the two: >> >> Nothing, Nowher

Re: [Cosign-discuss] This friggin' sucks....

2009-03-06 Thread Andrew Mortensen
This thread wandered into the weeds a while ago. It's now closed. On Mar 6, 2009, at 12:05 PM, Trek Glowacki wrote: > > On Mar 4, 2009, at 6:08 AM, Peter Schober wrote: > >> * Trek Glowacki [2009-03-03 21:24]: >>> So, to a third party observer both versions of the Cosign Equation >>> evaluate to

[Cosign-discuss] CosignRequireFactor OR Functionality?

2009-03-06 Thread Joshua West
Is it possible to use the CosignRequireFactor apache filter directive to specify that a user must satisfy factor A *OR* factor B? -- Joshua West Senior Systems Engineer Brandeis University http://www.brandeis.edu -- Ope

Re: [Cosign-discuss] CosignRequireFactor OR Functionality?

2009-03-06 Thread Jarod Malestein
Currently, no. The options are to either allow any authenticated user or, via CosignRequireFactor, only allow users that have satisfied the specified authN mechanisms. There is also an AllowPublicAccess option which will show a web page to authenticated or un-authenticated users. Jarod