If you have a streaming application, you rightfully want to protect your commissioned and original content from illegal activities.

You don ’ t want people to record any content and share it or distribute it. To prevent this, you might be adding extra DRM protection method into the SDKs or playback logic, which is responsible for pullulate the content from theCDNserver to the device.

What we feature observed is that many of the big streaming companies are not building their own Playback handler, so they are using SDKs (typically called Player SDK) to protect their content.

These Player SDKs often experience establish in protections, and commonly do similar security sensing to what a Secure SDK would do, such as detecting:

• Root/Jailbreak

• Repackaging and code injection

• Developer mode enable

• Screen Recorder tools running on the device

• Screenshot puppet and methods

Third party Player SDKs do not expose how they protect content, which get it unmanageable to run these coating in cloud establish devices or on devices where screen recording or screen grabbing is enable. All these tools are required to try and formalise these applications in a remote environment. There are many more, but a few examples of these SDKs are:

• Widevine DRM

• Bitmovin

• THEOplayer

• Microsoft PlayReady

What ’ s the issue?

When trial employ these Player SDKs are run on Sauce Labs, there could be some subject include a black or blurred blind when establish the app or opening a blind with DRM protect message. This is full news since your Player SDK is protecting the content properly! But you nevertheless need to test that the video stream works.

How can you see the content?

On Android device, you can enable the from your app scope if your DRM protection in the Player SDK is expend theFLAG_SECURE method.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

If that doesn ’ t work, there is a chance that the Player SDK employ for streaming is habituate additional hardening that is more stringently secured and/or utilize reflections.

For both Android and iOS, you can create a new build target/gradle target in order to lower the security in your Player SDK. This is usually an additional flag to surpass to the SDK, or you can use the DEBUG adaptation of the SDK.

For functional exam, we recommend creating a freestanding QA/TEST build mark, with a lower security restriction in the Player SDK (disable screenshot and recording protection).

This is how you cancreate a new chassis quarry in iOS/iPadOS in Xcode. 

And this is how you canconfigure your build discrepancy and production look on Android.

Will these builds work on Sauce Labs?

The player SDKmightdetect the following:

• Root/Jailbreak (incorrectly)

• Repackaging and codification injection

• Developer mode enabled

• Screen Recorder tools run on the device

In this case, an error content would look on the screen when the app is launched, or you might be unable to view protected content.

What ’ s the solution?

The result is the same as above: use a separate build target/variant with lowered PlayerSDK restrictions. Then upload these applications to Sauce.

Conclusion

Testing your message and the correct workflow in a gimmick cloud platform allows for efficient and thorough testing across a wide range of devices and platforms. This reduce the risk of bug or issues that may arise on specific device and OS combinations; and it check that these issues are not going to appear on product.

You will need to quiz DRM security exclusively once–that it works efficiently–so you can focus the rest of your testing efforts at the right job logic establishment. You can always test your SDK with lower level component or unit tests, to ensure the DRM protection is enabled before production freeing.

This helps to ascertain that your application is streaming the correct content, with the correct sound and video quality your business requires. This can save clip and resources for you, as your teams no longer need to buy and maintain a wide range of physical devices.