search for: 8a3642aac316

...ounds like a (bearer) token in combination with URL-auth would be a more promising thing to look into. http://icecast.org/docs/icecast-2.4.1/auth.html#url Basically you pass along a token to the listener software, e.g. like this: http://stream.example.org/music.opus?token=a0db5c27-f42c-4b81-85db-8a3642aac316 The token can be anything you choose, but you MUST control it. This means you generate the token e.g. during login to your website and then render URLs for that user with the token embedded into them. Then once they arrive at Icecast, it will make a request to your internal authentication endpoint...

I would like to have a private signal, which can only be tuned by whoever has the username and password, and know who is connected. But I wish the URL could be delivered with the username and password, to open it directly on a player or receiving device... Thanks. El sáb., 14 sept. 2019 a las 21:33, Marvin Scholz (<epirat07 at gmail.com>) escribió: > > > On 14 Sep 2019, at 21:09,