Re: Persisting data across authenticate <-> authorize ?

[prev] [thread] [next] [Date index for 2004/12/10]

Tim Pushor wrote:
> Hi modperl list
> 
> First of all, I am so excited to have discovered mod_perl. I have been 
> writing modules in C for a while now, and have been porting an old 
> module that used to work under Apache 1.2 to work on Apache 1.3 and am 
> having trouble for various reasons. I picked up mod_perl and in less 
> time than porting an old (already had been in production) module to a 
> new environment, I have almost completely re-written the module in perl. 
> Oh why didn't I do this sooner ;-)
> 
> My real question is this: I am writing an authentication / authorization 
> module. For various reasons, the authenticatoin portion determines 
> various things about the user in order to provide succesfull 
> authentication. This information can then be used later, in the 
> authorization module. I would like to cache this information somehow so 
> that the authorization handler doesn't need to perform these operations 
> over. I am already using IPC::Shareable in the authentication handler 
> and would prefer to not use that mechanism. Is there a way to have the 
> data persist across the authenticate/authorize parts of the module?

If you are just trying to have data that you set in the authentication 
be seen in the authorization phase you could just use $r->pnotes().

http://perl.apache.org/docs/1.0/api/Apache.html#_r_E_gt_pnotes___key____value___


        -- 
        Michael Peters
Developer
Plus Three, LP


-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html