Authentication for token-protected stream about radio-api HOT 4 CLOSED

Fair!
I guess what is needed is a kind of service that handles authentication and provides a redirect from the source URL.
This could be a service different to Radio-API all together.

from radio-api.

Hi,

the <EncryptedToken>3a3f5ac48a1dab4e</EncryptedToken> is always the same and also returned by Radio-API (https://github.com/KIMB-technologies/Radio-API/blob/master/php/index.php#L30C38-L30C54). As far as I know, this token is used by the radio to validate that it connected to a working api server.

Did you test to set one of the following urls for the station:

• http://shim-pri.wifiradiofrontier.com/vtuner/radio/1022963300812989/play/de_8_rob29?
• http://redirect.airable.io/1807976396573832

The requests/ responses before these urls seem to be equal to the ones sent by Radio-APIs.

1807976396573832 seems to be the ID of BBC used by Silicone Frontier. I then assume that http://redirect.airable.io/1807976396573832 does the token generation on the server side and redirects to the correct token/ streaming url each time it gets a request.

from radio-api.

Thanks for your response.
So far, using both http://redirect.airable.io/1807976396573832 and also http://a.files.bbci.co.uk/ms6/live/344XXXXX-XXXX-XXXX-XXXX-XXXXXXXXXA4B/audio/simulcast/dash/uk/pc_hd_abr_v2/cf/bbc_radio_fourfm.mpd still work.
I expected they would expire in line with the JWT, but that doesn't seem to be the case.

from radio-api.

Hi,
as long as these links work, I would not make any changes to Radio-API.
If such links do not exist any more, we will need to consider it again.

from radio-api.