Icecast - Jul 2015 - auth advice

I have all listeners logging in via htpasswd.
 I also have a playlist builder WEB app that I want to protect with the same
passwords.
 How can I use the password file generated by icecast web admin in an
apache-usable way
 for the playlist app.
 I've been synching this manually for a few users.
 
-- 
************************************************************************
*   Dave Serls                                 Littleton, CO, USA      *
*   dashs.denver.co.us                         http://www.dashs.com    *
************************************************************************

Good morning,

On Sun, 2015-07-12 at 14:15 -0600, Dave Serls wrote:
> I have all listeners logging in via htpasswd.
>  I also have a playlist builder WEB app that I want to protect with the
same passwords.
>  How can I use the password file generated by icecast web admin in an
apache-usable way
>  for the playlist app.
>  I've been synching this manually for a few users.
I think your best option is using the URL auth backend. So you have a
common database (of whatever type). Then your web app can communicate
with that database and Icecast can do the same using the URL Auth
backend.

You will find complete information on how to configure that backend in
the docs.

-- 
Philipp.
 (Rah of PH2)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
Url :
http://lists.xiph.org/pipermail/icecast/attachments/20150714/c51e1979/attachment.pgp