I filed the patch as:
https://issues.apache.org/bugzilla/show_bug.cgi?id=47295
Similar implementation shall also be possible on mod_dbd_session.
If necessary, I'll implement it next to the mod_authn_dbd.
This patch adds a two new directives (AuthDBDUserPWQueryFmt,
KaiGai Kohei wrote:
I'm now trying to set up mod_authn_dbb for authentication purpose.
However, I faced to a concern for AuthDBDUserRealmQuery directive.
The example shows the query:
AuthDBDUserRealmQuery \
SELECT password FROM authn WHERE user = %s AND realm = %s
But, I would
Chris Darroch wrote:
KaiGai Kohei wrote:
I think a new directive with formats support is preferable to
keep compatibility with existing directives.
We definitely need compatibility with existing directives.
That's why I figured the extra parameter would be optional --
if you only provided
Tom Donovan wrote:
KaiGai Kohei wrote:
I'm now trying to set up mod_authn_dbb for authentication purpose.
However, I faced to a concern for AuthDBDUserRealmQuery directive.
The example shows the query:
AuthDBDUserRealmQuery \
SELECT password FROM authn WHERE user = %s AND realm = %s
KaiGai Kohei wrote:
Tom Donovan wrote:
KaiGai Kohei wrote:
I'm now trying to set up mod_authn_dbb for authentication purpose.
However, I faced to a concern for AuthDBDUserRealmQuery directive.
The example shows the query:
AuthDBDUserRealmQuery \
SELECT password FROM authn WHERE user =
Tom Donovan wrote:
Yes, SQL *functions* only return a single value - but if your database
supports SQL *stored procedures* (like the example), they return a set
of rows; including any extra values to be assigned to environment
variables. For example:
DROP PROCEDURE IF EXISTS digest;
KaiGai Kohei wrote:
Tom Donovan wrote:
Yes, SQL *functions* only return a single value - but if your database
supports SQL *stored procedures* (like the example), they return a set
of rows; including any extra values to be assigned to environment
variables. For example:
DROP PROCEDURE
Tom Donovan wrote:
KaiGai Kohei wrote:
Tom Donovan wrote:
Yes, SQL *functions* only return a single value - but if your
database supports SQL *stored procedures* (like the example), they
return a set of rows; including any extra values to be assigned to
environment variables. For
KaiGai Kohei wrote:
I'm now trying to set up mod_authn_dbb for authentication purpose.
However, I faced to a concern for AuthDBDUserRealmQuery directive.
The example shows the query:
AuthDBDUserRealmQuery \
SELECT password FROM authn WHERE user = %s AND realm = %s
But, I would like to
I'm now trying to set up mod_authn_dbb for authentication purpose.
However, I faced to a concern for AuthDBDUserRealmQuery directive.
The example shows the query:
AuthDBDUserRealmQuery \
SELECT password FROM authn WHERE user = %s AND realm = %s
But, I would like to set up the query as
KaiGai Kohei wrote:
But, I would like to set up the query as follows:
AuthDBDUserRealmQuery \
SELECT md5(uname || ':' || %s || ':' || upass) FROM uaccount WHERE uname =
%s
^^... to be realmto be user
... ^^
It seems to me we have no
Chris Darroch wrote:
KaiGai Kohei wrote:
But, I would like to set up the query as follows:
AuthDBDUserRealmQuery \
SELECT md5(uname || ':' || %s || ':' || upass) FROM uaccount
WHERE uname = %s
^^... to be realmto
be user ... ^^
It
KaiGai Kohei wrote:
I think a new directive with formats support is preferable to
keep compatibility with existing directives.
We definitely need compatibility with existing directives.
That's why I figured the extra parameter would be optional --
if you only provided one parameter, the
13 matches
Mail list logo
