[icecast-dev] Client auth with mysql

[Dave St John]

One thing i would like to see with the mysql auth framework is this
<authentication type="mysql">
     <option name="dbname" value="database name here"/>
    <option name="dbuser" value="database username here"/>
    <option name="dbpass" value="database password here"/>
    <option name="db_table_prefix" value="database table prefix here"/> <!-- 
i.e. iceauth_ -->
    <option name="db_username_field" value="database field name
here"/><!--name of field to get usernames from username -->
    <option name="db_password_field" value="database field name here"/>
<!--name of db field to get password from i.e. userpass -->
</authentication>

That way we can specify what db to use and just about all hte options you
would want to see.

then the sql would look something like this

CREATE TABLE `subscription_servers` (
  `server_id` int(11) NOT NULL default '0',
  `subscriber_id` varchar(55) NOT NULL default '0',
  `username` varchar(255) NOT NULL default '',
  `userpass` varchar(255) NOT NULL default '',
  `raw_password` varchar(255) NOT NULL default '',
) TYPE=MyISAM;

<p><p>Dave St John
Mediacast1 Administration

Need Support ?
http://mediacast1.com/helpdesk
----- Original Message ----- 
From: "Mathieu Arnold" <mat at mat.cc>
To: <icecast-dev at xiph.org>
Sent: Thursday, May 13, 2004 3:12 AM
Subject: Re: [icecast-dev] Client auth with mysql

<p>> +-Le 12/05/2004 14:20 -0500, oddsock a dit :
> | Mathieu,
> |
> | This is a great idea, and I'm sure many people would like to take
> | advantage of it.  Since the release of 2.0.0, we've added an
> | "authenticator" framework which allows us to create authentication
> | modules for handling listener (client-based) authentication.  We
> | currently have one authentication module (htpasswd) which uses a simple
> | file to store users and encrypted passwords.  With this new framework,
> | adding additional authenticators (URL, mysql, etc.) should be fairly
> | simple, or at least that's the intent...
> |
> | as you patch stands right now, I'm not sure it will be adopted, however
> | the chances are very good if you re-write it using the authenticator
> | framework that is currently in the most current Subversion repository...
>
> Ok, I knew what I was doing wasn't the right way to do it :-)
>
> I'll have a look at this auth framework, thanks for the feedback, I feel
> less alone know ;-)
>
> -- 
> Mathieu Arnold
> --- >8 ----
> List archives:  http://www.xiph.org/archives/
> icecast project homepage: http://www.icecast.org/
> To unsubscribe from this list, send a message to
'icecast-dev-request at xiph.org'
> containing only the word 'unsubscribe' in the body.  No subject is needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
>

<p>--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-dev-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.