Hi Darren
Would you submit the current version? If you need help with the
Documentation just let me know. For the makefile, I do not have any
experience.
Marcel
Am Mittwoch den, 13. Februar 2002, um 21:01, schrieb darren chamberlain:
> Quoting Marcel Weber <[EMAIL PROTECTED]> [13 Feb-02 14:5
At 17:21 13.02.2002 -0600, you wrote:
>File::Spec is in included with the standard perl mods I believe
>so dependencies shouldn't be a problem.
>
> > I see. You're right, this is actually much nicer!
> >
> > Sorry for the misinformation. On debian it return : also. I made a
> > mistake checking it
File::Spec is in included with the standard perl mods I believe
so dependencies shouldn't be a problem.
> I see. You're right, this is actually much nicer!
>
> Sorry for the misinformation. On debian it return : also. I made a
> mistake checking it.
>
> But with the suggested code by Per it wo
I see. You're right, this is actually much nicer!
Sorry for the misinformation. On debian it return : also. I made a
mistake checking it.
But with the suggested code by Per it works just fine:
sub load {
my $module=@_[0];
$module = File::Spec->catfile(split /::/, $module);
$modu
Cool . . .
Thanks for the tip : )
> > > The easiest thing would be to use Config, and do:
> > >
> > > $module =~ s[::][$Config{'path_sep'}]g;
> > >
> > > Right?
> >
> >Maybe not : ) When checking on 2 linux systems I got a path seperator of
> >':'. Can you let me know if you get similar resu
Sorry, this code does not work... Should test it better before sending
it to to mailing list...
Marcel
Am Donnerstag den, 14. Februar 2002, um 00:05, schrieb Marcel Weber:
> So here comes the most actual code:
>
> Submitting it to CPAN would be fine!
>
> ---
Interesting, one system is RedHat 7.2 and Suse 7.3 (custom built perl) that
returns
a ':' for $Config{'path_sep'}
> It returns a arrayref, as far as I experienced. Well I'm really new to
> mod_perl
> and my eagle book waits still in the library to be bought... But why is
> this
> version not ni
At 16:51 13.02.2002 -0600, Stathy G. Touloumis wrote:
> > The easiest thing would be to use Config, and do:
> >
> > $module =~ s[::][$Config{'path_sep'}]g;
> >
> > Right?
>
>Maybe not : ) When checking on 2 linux systems I got a path seperator of
>':'. Can you let me know if you get similar re
On my woody system it's fine.
Marcel
Am Mittwoch den, 13. Februar 2002, um 23:51, schrieb Stathy G. Touloumis:
>> The easiest thing would be to use Config, and do:
>>
>> $module =~ s[::][$Config{'path_sep'}]g;
>>
>> Right?
>
> Maybe not : ) When checking on 2 linux systems I got a path seper
So here comes the most actual code:
Submitting it to CPAN would be fine!
package Apache::AuthMulti;
# Stathy G. Touloumis
# Marcel M. Weber
# Darren Chamberlain
#
# Version 0.01-2 / 13.02.2002 / Marcel M. Weber
use strict;
use Apache::C
> The easiest thing would be to use Config, and do:
>
> $module =~ s[::][$Config{'path_sep'}]g;
>
> Right?
Maybe not : ) When checking on 2 linux systems I got a path seperator of
':'. Can you let me know if you get similar results?
Thanks,
> > I would suggest changing the PerlSetVar variables
> > to actual apache configuration directives which would change this :
> >
> > my @auth_modules=$r->dir_config->get("AuthModules");
> >
> > I don't have an immediate patch for this but have done it before.
> > If you would like me to work on
Quoting Stathy G. Touloumis <[EMAIL PROTECTED]> [13 Feb-02 15:26]:
> Some more fixes ; )
Yay! Bug reports already...
> I would suggest changing the PerlSetVar variables
> to actual apache configuration directives which would change this :
>
> my @auth_modules=$r->dir_config->get("AuthModules");
Some more fixes ; )
I would suggest changing the PerlSetVar variables
to actual apache configuration directives which would change this :
my @auth_modules=$r->dir_config->get("AuthModules");
I don't have an immediate patch for this but have done it before.
If you would like me to work on this c
>
>
> I think you might need to iterate through $r->err_headers_out and
> remove WWW-Authenticate and Proxy-Authenticate after each
> authentication module runs.
>
> say you have an AuthSMB and AythSybase chain. AuthSMB calls
> note_basic_auth_failure and sets the WWW-Authenticate header,
> A
Marcel Weber wrote:
>
> Fixed some errors. Here comes the working version:
>
I think you might need to iterate through $r->err_headers_out and
remove WWW-Authenticate and Proxy-Authenticate after each
authentication module runs.
say you have an AuthSMB and AythSybase chain. AuthSMB calls
no
Quoting Marcel Weber <[EMAIL PROTECTED]> [13 Feb-02 14:53]:
> Why not submitting this somewhere? I think this could be
> usefull for quite a lot of people. I think this is cool, as you
> do not have to worry wether the module returns DECLINED or
> AUTH_REQUIRED.
I can package this up and put it o
Fixed some errors. Here comes the working version:
-
package Apache::AuthMulti;
# Stathy G. Touloumis
# Marcel M. Weber
# Darren Chamberlain
#
# Version 0.1.0 / 2002.02.13 / Marcel M. Weber
use strict;
use Apache::Constants qw(:common);
sub handler {
my $r = shift;
> the only problem is that,
> for the PerlAuthenHandler and PerlAuthzHandler the first handler to
> return an Apache error code (anything other than OK, DECLINED, or
> DONE) terminates the chain. which is generally fine, except when you
> want to return AUTH_REQUIRED and note_basic_auth_failure()
Aaron Ross wrote:
>
> shouldn't stacked handlers be the right solution here? are stacked auth
> handlers not allowed or something?
>
yes, you can stack multiple auth handlers. the only problem is that,
for the PerlAuthenHandler and PerlAuthzHandler the first handler to
return an Apache error
He wants to check a 'handler' return value.
> shouldn't stacked handlers be the right solution here? are stacked auth
> handlers not allowed or something?
>
> aaron
>
> On Wed, 2002-02-13 at 09:02, darren chamberlain wrote:
> > Quoting Marcel Weber <[EMAIL PROTECTED]> [12 Feb-02 16:15]:
> > >
Quoting Aaron Ross <[EMAIL PROTECTED]> [13 Feb-02 09:21]:
> shouldn't stacked handlers be the right solution here? are
> stacked auth handlers not allowed or something?
Assuming your mod_perl has been built with them, then, yes, that's
probably a better solution. But I had a fun 15 minutes writ
shouldn't stacked handlers be the right solution here? are stacked auth
handlers not allowed or something?
aaron
On Wed, 2002-02-13 at 09:02, darren chamberlain wrote:
> Quoting Marcel Weber <[EMAIL PROTECTED]> [12 Feb-02 16:15]:
> > I don't get the point why it did not work the other way round
Quoting Marcel Weber <[EMAIL PROTECTED]> [12 Feb-02 16:15]:
> I don't get the point why it did not work the other way round,
> but now everything is just fine now :
Make it a little more generic:
package Apache::MultiAuthen;
use strict;
use Apache::Constants qw(:common);
sub handler {
my $
turn Apache::Constant::AUTH_REQUIRED;
> }
>
> Marcel
>
>
> -Ursprüngliche Nachricht-
> Von: Stathy G. Touloumis [mailto:[EMAIL PROTECTED]]
> Gesendet: Dienstag, 12. Februar 2002 18:32
> An: Marcel Weber; [EMAIL PROTECTED]
> Betreff: RE: Multiple authenticatio
Perhaps it is my
> mod_perl installation. It is a stock Debian Woody installation.
>
> Marcel
>
>
> -Ursprüngliche Nachricht-
> Von: Stathy G. Touloumis [mailto:[EMAIL PROTECTED]]
> Gesendet: Dienstag, 12. Februar 2002 18:32
> An: Marcel Weber; [EMAIL PROTECTED]
> B
> The get_handlers code is out of AuthenSmb as I do not have the slightest
> idea of how to get the results of the called function.
Hmmm, It would seem that it would be better to call the function directly
from your handler. I am not sure how the AuthenSmb handlers should be
called but you should
>
>
>AuthName Test
>AuthType Basic
>PerlSetVar myPDC SAMBA
>PerlSetVar myDOMAIN ARBEITSGRUPPE
>PerlAuthenHandler Apache::AuthenSmb Apache::AuthSybase
>require valid-user
>
>
is mod_perl compiled with STACKED HANDLERS?
the first module to run will need to return DECLIN
28 matches
Mail list logo
