[Icecast-dev] URL authentication

[Klaas Jan Wierenga]

In my case that's not needed, but yes it would be really nice if all 
mount options could be retrieved from the database using an 
authenticated URL.

KJ

Stefan de Konink wrote:
> On Fri, 8 Sep 2006, Klaas Jan Wierenga wrote:
>
>   
>> I guess if the <authentication type="url> section could be used as a
>> top-level tag (instead of  as a sub-tag of <mount>), then  that could do
>> the trick.  The mount_add URL would be used to check the validity of
>> the/any mountpoint. The listener_add authenticates the users.
>>
>> Would this be hard to implement? It would certainly make administration
>> a lot easier for icecast users that keep mountpoint names, username and
>> passwords in a database.
>>
>> Any help would be appreciated.
>>     
>
> I think the implementation is not that hard, but is this the only thing
> you want to store for your customer, not things like: bandwidth, max
> users?
>
>
> Probably it could be more easy to store all mounts in SQL, and fetch
> info on aauthentication.
>
>
>
> Stefan
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xiph.org/pipermail/icecast-dev/attachments/20060908/3b95ff2e/attachment.html