Enterprise Product Update: Change to Streaming Events Authentication

Enterprise Product Update: Change to Streaming Events Authentication

On Sunday, 11 October 2020 starting from 03:00 to 04:00 UTC we will be simplifying the method in which StreamShark users authenticate their live streaming events for all customers with dedicated Ingests. Over the course of this hour long maintenance window, be prepared for intermittent downtime of your dedicated live streaming servers.

This change will only impact the StreamShark dedicated servers. Enterprise customers using shared (multi-tenanted) servers were migrated to this authentication method in late March 2020. 

After this maintenance window is complete, users with dedicated ingests will no longer be required to authenticate using a separate username and password. Your events will instead leverage the inline authentication already present within the ‘Stream Name’ field. Any event created after the 29th March 2020 will have this authentication information already in the ‘Stream Name’ field and will not be impacted by this change. If you have an event pre-configured in your streaming software or hardware with a username and password set, these will be ignored, however this will not impact the authentication process.

This change will make it faster to set up streams within your live encoder, and it will also vastly increase the compatibility of StreamShark with a wider range of software and hardware live encoding solutions, as well as video conferencing solutions like Zoom.

You will be able to tell if the server you’re using has the new authentication method by looking at what’s displayed in the ‘Publishing URLs’ section of your ‘Event Overview’ tab. Below you can see how the ‘Publishing URLs’ section will look after the change.

Before:

After:

If you have any questions or issues please don’t hesitate to contact our support team by emailing support@streamshark.io or using the red support button inside the StreamShark dashboard.

Leave A Comment

Your email address will not be published. Required fields are marked *