Hash-Based token doesn't work properly in HLS Stream with Adaptive Streaming.

[Ben Bowler]

We're setting up the hash-based tokens across the app, publish and play over WebRTC is working great but HLS files are now all returning 403 errors:

I notice that it's the same issues as SelimEmre did here back in 2020. Was this issue fixed?

We're on: 

• Enterprise Edition 2.2.1 20201029_2042

 

 

[Ben Bowler]

For more context, HLS with token does not work either with adaptive bitrate or single bitrate. This is the example URL from the preview:

liveLocal/play.html?name=live_1d06cfef4014542fee28d89b43e7f323e24a_event_83d98aae6b66a670190d3ce6d5051162ce12&token=e5372b7fa882587429600effc9f95e2d1be0c67334cf3e99e4b8a262bd989845&playOrder=hls

If I remove playOrder=hls it plays fine in the WebRTC Mode.

 

[Ben Bowler]

I've confirmed that the tokens match in the settings and restarted the server.

 

 

[Selim Emre]

Hi Ben,

Thanks for reporting us!

I have tried with stream1 and it worked. But it couldn't work with your stream ID(live_1d06cfef4014542fee28d89b43e7f323e24a_event_83d98aae6b66a670190d3ce6d5051162ce12). 

For the workaround solution, is it possible to use with live-1d06cfef4014542fee28d89b43e7f323e24a-event-83d98aae6b66a670190d3ce6d5051162ce12

Also I have add an issue for you -> https://github.com/ant-media/Ant-Media-Server/issues/3217

I hope, I could help you.

Best Regards,

Selim

[Ben Bowler]

Ah great! I had a similar issue with application names, I noticed that the application name live_dev does not work. 

On 28 Apr 2021, 19:06 +0100, Selim Emre <selimemretoy@gmail.com>, wrote:

Hi Ben,

Thanks for reporting us!

I have tried with stream1 and it worked. But it couldn't work with your stream ID(live_1d06cfef4014542fee28d89b43e7f323e24a_event_83d98aae6b66a670190d3ce6d5051162ce12). 

For the workaround solution, is it possible to use with live-1d06cfef4014542fee28d89b43e7f323e24a-event-83d98aae6b66a670190d3ce6d5051162ce12

Also I have add an issue for you -> https://github.com/ant-media/Ant-Media-Server/issues/3217

I hope, I could help you.

Best Regards,

Selim

 

--

You received this message because you are subscribed to a topic in the Google Groups "Ant Media Server" group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/ant-media-server/8S4xkStPAa4/unsubscribe.

To unsubscribe from this group and all its topics, send an email to ant-media-server+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ant-media-server/04f12914-4404-414e-9cf9-fd36f68e1aa0n%40googlegroups.com.

[Ben Bowler]

I’ll try this tomorrow. 

On 28 Apr 2021, 19:06 +0100, Selim Emre <selimemretoy@gmail.com>, wrote:

Hi Ben,

Thanks for reporting us!

I have tried with stream1 and it worked. But it couldn't work with your stream ID(live_1d06cfef4014542fee28d89b43e7f323e24a_event_83d98aae6b66a670190d3ce6d5051162ce12). 

For the workaround solution, is it possible to use with live-1d06cfef4014542fee28d89b43e7f323e24a-event-83d98aae6b66a670190d3ce6d5051162ce12

Also I have add an issue for you -> https://github.com/ant-media/Ant-Media-Server/issues/3217

I hope, I could help you.

Best Regards,

Selim

 

--

You received this message because you are subscribed to a topic in the Google Groups "Ant Media Server" group.

To unsubscribe from this topic, visit https://groups.google.com/d/topic/ant-media-server/8S4xkStPAa4/unsubscribe.

To unsubscribe from this group and all its topics, send an email to ant-media-server+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ant-media-server/04f12914-4404-414e-9cf9-fd36f68e1aa0n%40googlegroups.com.