We have made improvements to increase security, so password authorization on Slicer login will no longer be supported after March 25, 2019. Instead, we will require API key authentication.
On March 25th, 2019, we are planning a global change affecting all customers who have not implemented API keys. This change will impact the streaming service of those customers. After this change, there will no longer be support for the password entry on Slicer login and customers will be required to use API key authentication.
Please take the following action by March 24th to ensure your streaming service is not affected:
-
Update the Live Slicer to version 17111500 (11/22/2017) or higher, to have support for API keys. We recommend that you update to the latest Slicer release which can be downloaded from the Uplynk CMS.
-
Update your Slicer configuration to leverage API key authorization, instead of password authorization. Learn More
Note: Our original request to comply went out June 25, 2018. If you have already implemented API key authentication, you can disregard this request and you will not be affected.
For any questions or concerns please contact your Technical Account Manager or our support team at [email protected] or 1-877-334-3236.
Additions:
-
SCTE logging function
-
Allow for metadata to be supplied with boundary calls
Fixes:
-
Timecode flag crashes LiveSlicer
-
External ID not populating in CMS
-
Add_cc608 endpoint causing segfault
-
Slicer Improperly pre-ingests schedule on start up
-
Linear channel jitters / judders
-
Dropped_frame_usec does not reset on content start
-
Return values for bug timing in MS
Known Issues:
-
Image bugs do not display in Live Slicer with SDI mode
-
Windows GUI Slicer can’t login. Please use previous release for password authorization in Windows GUI Slicer.
Download the latest
Updating your slicer keeps you on the cutting edge of what our platform has to offer. Don't delay
We are making improvements to increase security, so password authorization on Slicer login will no longer be supported after March 25, 2019. Instead, we will require API key authentication.
On March 25th, 2019, we are planning a global change affecting all customers who have not implemented API keys. This change will impact the streaming service of those customers. After this change, there will no longer be support for the password entry on Slicer login and customers will be required to use API key authentication.
Please take the following action by March 24th to ensure your streaming service is not affected:
-
Update the Live Slicer to version 17111500 (11/22/2017) or higher, to have support for API keys. We recommend that you update to the latest Slicer release which can be downloaded from the Uplynk CMS.
-
Update your Slicer configuration to leverage API key authorization, instead of password authorization. Learn More
Note: Our original request to comply went out June 25, 2018. If you have already implemented API key authentication, you can disregard this request and you will not be affected.
For any questions or concerns please contact your Technical Account Manager or our support team at [email protected] or 1-877-334-3236.
Additions:
-
Upload queue depth to status API
-
cc1_on parameter to suppress individual 608 channels in LiveSlicer
Fixes:
-
An issue where the slicer would generate malformed slices
-
Regression causing "Slicer version doesn't support ad breaks in dash live stream. Upgrade slicer" errors on dash playback
-
Issue with FPS reduction
-
Errors in SliceBot job failure
-
Removed slicer failover group configuration (moved to services API)
-
Issue where a SCTE break was inserting two breaks instead of one
Download the latest
Updating your slicer keeps you on the cutting edge of what our platform has to offer. Don't delay
Additions:
-
Track additional information in slicer status for monitoring backend
-
Configuration example files for apikey usage
Fixes:
-
Slicer dropping frames periodically in DR mode
-
Unexpected ad breaks appearing
-
Recovering SCTE processing after slicer restart
-
Nielsen ID3 message box signaling in DASH
-
A SCTE segfault
-
Anamorphic video and image overlays
-
Stats reporting for NIC I/O bonded interfaces
-
max_no_signal_time configuration in linux
-
host NTP drift from server time automatically for apikey authentication
-
Ad break signaling for DASH
-
Python plugin dynamic linkage issue
Download the latest
Updating your slicer keeps you on the cutting edge of what our platform has to offer. Don't delay
Today we’ve added the following Test Player features to improve content security.
-
Prevent your account from auto creating test players in Settings > Test Player Restriction. This will be disabled by default.
-
New test player access permissions in Settings > Account Access let you specify who can create (write) and view (read) test players. All current users will have read & write permissions.
-
When creating new test players, you can restrict playback to only whitelisted IP addresses and set an expiry duration. Your whitelist can be configured in Settings > Test Player Restrictions.
The Uplynk settings tab has been refreshed. While none of the settings have changed, we did update a few section names:
Account Settings is now User Settings
Playback Tokens is now Integration Keys
Stream Domains is now Playback Restrictions
Pod Formats have been added to Live Event configurations. They allow you setup individual, predefined ad pods for your events that include durations and custom key/value pairs. To accommodate these changes you'll notice a slighly new layout to your Live Event Dashboard.
More details on this new feature can be found at https://support.uplynk.com/doc_live_events_2.html
Starting June 27th, 2018 your Uplynk CMS username and password will be managed by Verizon Digital Media Services Identity Management Service (IDS). IDS will increase security and provide a single identity that can be used across all VDMS properties.
Migration Process
-
The first time logging into Uplynk between 6/27/2018 and 8/01/2018, you will need to verify, change or add an email associated with your account
-
Make sure to have access to the inbox associated with this address
-
If you've already created an IDS identity for other VDMS services, this identity will be associated with your Uplynk account
-
Next, you will be directed to the IDS reset password page to create a new password using your email on file
-
That's it! Moving forward you'll be presented with the IDS login page whenever you navigate to cms.uplynk.com
-
Please make sure to migrate your account by August 1st
Important Notes
- Your CMS and Slicer identities will be managed separately and can be accessed in Settings > Account Settings
- These changes will have no impact on your API or Application Keys
New Slicer Requirements
-
Starting 8/1/2018, any Slicer & Live Slicer Software older than Release 17111500 dated 11/22/2017 will no longer connect to your Uplynk service and will no longer be supported.
-
Slicer authentication using API keys will be required and Slicer Release 17111500 or newer will be required to enable the API Keys
-
Download the latest Slicer Release via the Uplynk CMS before 8/1/2018 then click HERE to learn how to setup your slicers with API Keys
For any questions or concerns please contact your Technical Account Manager or our support team at [email protected] or 1-877-334-3236