Fedora Core 2, Apache 2, and Auth_MySQL_Info
I'm performing an upgrade of one of my web servers from an old Debian release running Apache 1.3.
So I loaded Apache and relevant modules using yum, and and turned it on. Success!
Next, I started the conversion of my old 1.3 httpd.conf well into it, and added this:
LoadModule mysql_auth_module modules/mod_auth_mysql.so
This loaded correctly.
Now, I moved onto the section of a virtual host.
Contained within that virtual host was a line that made all the PHP calls in the website authenticate against the mySQL database:
Auth_MySQL_Info localhost <usernamedeleted> <passworddeleted>
When I started up apache, I get:
Syntax error on line 1762 of /etc/httpd/conf/httpd.conf:
Invalid command 'Auth_MySQL_Info', perhaps mis-spelled or defined by a module not included in the server configuration
And, lo and behold, checking /server-info verifies that the Directive isn't included.
Module Name: mod_auth_mysql.c
Content handlers: none
Configuration Phase Participation: Create Directory Config
Request Phase Participation: Verify User ID, Verify User Access
AuthMySQLHost - mysql server host name
AuthMySQLUser- mysql server user name
AuthMySQLPassword - mysql server user password
AuthMySQLDB - mysql database name
AuthMySQLUserTable - mysql user table name
AuthMySQLGroupTable - mysql group table name
AuthMySQLNameField - mysql User ID field name within table
AuthMySQLGroupField - mysql Group field name within table
AuthMySQLPasswordField - mysql Password field name within table
AuthMySQLCryptedPasswords - mysql passwords are stored encrypted if On
AuthMySQLScrambledPasswords - mysql passwords are stored scrambled if On
AuthMySQLMD5Passwords - mysql passwords are stored as MD5 if On
AuthMySQLKeepAlive - mysql connection kept open across requests if On
AuthMySQLAuthoritative - mysql lookup is authoritative if On
AuthMySQLNoPasswd - If On, only check if user exists; ignore password
AuthMySQLUserCondition - condition to add to user where-clause
AuthMySQLGroupCondition - condition to add to group where-clause
Now, checking the module readme, there was a bug in pre version 4.21 releases of the code which caused this. However, that's very old code, and I would guess the code is newer....
I'd like to ensure that my system is still well maintained with yum and automated tools -- thus I don't want to do download the module code and recompile unless it really isn't possible to do any other way.
Can someone help?