I have two tables: users and userurls the join is on users.user_id = userurls.user.id and the where clause is on a row in userurls (userurls.url_id = 5)
So my in my httpd.conf is says:
AuthMySQLUserCondition = "users_user_name = userurls_user_name and url_id ='5' "
But it returns an error: AuthMySQLUserCondition takes one argument, condition to add to user where-clause
Well, it looks like there's been a change in the way Apache handles configuration directives - at least from the .htaccess file.
We've been looking at this for a while, but it hasn't been a problem until now. However, it looks like we're going to have to resolve this problem - this is a parameter which may have more than one value, and we don't know how many it will have (there are others, also).
There is a way around it for your situation, however, and that's the use of groups, something like:
Now - this requires the user name field in your GroupTable to match that in your UserTable (in this case, user_name). If you can change this in the table, fine.
If you can't, the next version has a new parameter AuthMySQLGroupUserNameField which will allow you to use a different column name for your user name. This version is currently in final test and the documentation is being updated. (I had hoped to have it out by now, but testing found a bug). It may be available this week, but as I'll be out of the office at least two days, I'm not positive on that.
If you can't change the name of the field and can't wait, I can send you the version currently being tested. Let me know, and if you wish an email address other than your sourceforge one, please pass that address on to me as well (in email, if you wish, to my sourceforge address).
Sorry for the problem - this one caught us by surprise.
Jerry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have two tables: users and userurls the join is on users.user_id = userurls.user.id and the where clause is on a row in userurls (userurls.url_id = 5)
So my in my httpd.conf is says:
AuthMySQLUserCondition = "users_user_name = userurls_user_name and url_id ='5' "
But it returns an error: AuthMySQLUserCondition takes one argument, condition to add to user where-clause
Further it says:
AuthName "Centrale Agenda"
AuthType Basic
AuthMySQLUser xxxxx
AuthMySQLPassword yyyyy
AuthMySQLDB zzzzzz
AuthMySQLUserTable "users, userurls"
AuthMySQLNameField user_name
AuthMySQLUserCondition = "users_user_name = userurls_user_name and url_id ='5' "
AuthMySQLPasswordField user_passwd
require valid-user
What is going wrong here?
Running FC3 and Apache 2.0.52
Hi, Marc,
Well, it looks like there's been a change in the way Apache handles configuration directives - at least from the .htaccess file.
We've been looking at this for a while, but it hasn't been a problem until now. However, it looks like we're going to have to resolve this problem - this is a parameter which may have more than one value, and we don't know how many it will have (there are others, also).
There is a way around it for your situation, however, and that's the use of groups, something like:
AuthName "Centrale Agenda"
AuthType Basic
AuthMySQLUser xxxxx
AuthMySQLPassword yyyyy
AuthMySQLDB zzzzzz
AuthMySQLUserTable users
AuthMySQLNameField user_name
AuthMySQLPasswordField user_passwd
AuthMySQLGroupTable userurls
AuthMySQLGroupField url_id
require group '5'
Now - this requires the user name field in your GroupTable to match that in your UserTable (in this case, user_name). If you can change this in the table, fine.
If you can't, the next version has a new parameter AuthMySQLGroupUserNameField which will allow you to use a different column name for your user name. This version is currently in final test and the documentation is being updated. (I had hoped to have it out by now, but testing found a bug). It may be available this week, but as I'll be out of the office at least two days, I'm not positive on that.
If you can't change the name of the field and can't wait, I can send you the version currently being tested. Let me know, and if you wish an email address other than your sourceforge one, please pass that address on to me as well (in email, if you wish, to my sourceforge address).
Sorry for the problem - this one caught us by surprise.
Jerry
Marc,
One other thing - please add this to the bug database so we can ensure it gets fixed. Thanks,
Jerry