Skip Menu |

This queue is for tickets about the Apache-DBI CPAN distribution.

Report information
The Basics
Id: 69316
Status: open
Priority: 0/
Queue: Apache-DBI

People
Owner: Nobody in particular
Requestors: MRDVT [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 1.08
Fixed in: (no value)



Subject: Feature request "AUTHENTICATE_XXX" environment variables
When I use the LDAP auth provider in Apache it provides some "extra" AUTHENTICATE_XXX environment variables so that I don't have the hit the server again. I would like for Apache::AuthDBI to support this as well. LDAP Example is AuthBasicProvider ldap AuthLDAPUrl ldap://ldapserver:389/OU=_COMPANY,DC=COMPANY,DC=com? sAMAccountName,mail,name,extensionAttribute2,memberOf?base? (objectClass=user) All of the values "sAMAccountName,mail,name,extensionAttribute2,memberOf" are returned to the environment for use by the application. These are also cached with the authentication so that the application need not re-fetch these values AUTHENTICATE_EXTENSIONATTRIBUTE2 somedatahere AUTHENTICATE_MAIL email@address.xyz AUTHENTICATE_MEMBEROF ... AUTHENTICATE_NAME My Name AUTHENTICATE_SAMACCOUNTNAME correctedloginwithcase This is also consistent with Apache Module mod_authn_dbd http://httpd.apache.org/docs/2.2/mod/mod_authn_dbd.html If httpd was built against APR version 1.3.0 or higher, any additional column values in the first row returned by the query statement will be stored as environment variables with names of the form AUTHENTICATE_COLUMN.
Subject: Re: [rt.cpan.org #69316] Feature request "AUTHENTICATE_XXX" environment variables
Date: Wed, 6 Jul 2011 09:41:03 -0700
To: bug-Apache-DBI [...] rt.cpan.org
From: Ask Bjørn Hansen <ask [...] perl.org>
On Jul 6, 2011, at 9:38, Michael R. Davis via RT wrote: Show quoted text
> > When I use the LDAP auth provider in Apache it provides some "extra" > AUTHENTICATE_XXX environment variables so that I don't have the hit the > server again.
Why not just cache the result of the query in your application? I don't understand what this is supposed to do exactly.
Show quoted text
> Why not just cache the result of the query in your application?
Exactly, AuthDBI happens *before* the application even comes up so it is the first hit to the database! No, need in hitting the DB twice... If I could ever get apr-util-oracle complied and working then this would all be moot.