Re: Problem using PerlSection and global object in conf

2007-01-05 Thread Sean P Quinlan
On Thu, 2007-01-04 at 19:25 -0500, Perrin Harkins wrote: > Put that in a namespace so it won't get interpreted as a directive: > $My::Auth_admin = CAS::Apache::Auth->new({CLIENT_ID => > $CAS_admin_client}); > *nodnod* Thanks! > > Oops, I'm calling the method instead of setting it as a handler

Re: Problem using PerlSection and global object in conf

2007-01-05 Thread Sean P Quinlan
First off, let me apologize to everyone for not responding last night. I got a bounce message back and I assumed (yeah yeah) that it had not made it to the list. Not long after writing this email, I noticed a difference in the example in the docs to my code. I was creating an object in the current

Re: Problem using PerlSection and global object in conf

2007-01-04 Thread Perrin Harkins
On Thu, 2007-01-04 at 17:13 -0500, Sean P Quinlan wrote: > And here is the relevant portions of my configuration file (located in > conf.d/): > > $Apache2::PerlSections::Save = 1; > use CAS::Apache::Auth; > > # The default CAS client for the admin location > $CAS_ad

Re: Problem using PerlSection and global object in conf

2007-01-04 Thread Jonathan Vanasco
On Jan 4, 2007, at 5:13 PM, Sean P Quinlan wrote: The way the new version is designed, a 'client' object will cache the user objects (relatively small, name, email, phone etc) for users previously authenticated, using a session token as a key. Reading the document above, it seemed I would

Problem using PerlSection and global object in conf

2007-01-04 Thread Sean P Quinlan
I have an application I am in the process of upgrading to Apache/mod_perl 2. While reading the docs, I came across this section: http://perl.apache.org/docs/2.0/user/coding/coding.html#Method_Handlers Which I was really excited to try! My application handles user authentication and authorization,