Working with Kaltura partner 0
Working with Kaltura partner 0 is essential if you need to add a global entity to the Kaltura system. For example, if you would like to create and configure a player that can be used at all publishers in your Kaltura System, you need to add it to partner 0. This way, every one of your Kaltura publisher will be able to use the player. Of course you can replicate the same player for each publisher, but this will be a waste of your time and effort.
While assigning a player, which is represented by uiConf, is simple and all you need to do is to change the publisher id of the uiConf to 0, there are some entities that cannot be assigned to partner 0 via UI. In this case, you need to use the Kaltura API via the Developer console.
This is a good example for a global entity you may want to assign to partner 0, but have to use the API for this, because it’s a flavorAsset. A flavorAsset is a transcoding configuration for your video file and is configured in the ‘Transcoding Settings’ tab in every publisher’s KMC account.
In one of my latest migration projects, the client wanted to add new custom HLS flavors, but since he had several publishers on our Kaltura system, I had to create some global HLS flavours and the most efficient way to do it is to assign them to partner 0.
As I mentioned before, in order to assign a flavorAsset to partner 0 we need to use the Kaltura API. In order to make API calls to Kaltura you need a KS (Kaltura Session).
I have already explained about KS and how can retrieve it easily , but in order to get KS for partner 0, you need to do a little trick.
Now you have a KS for working with Kaltura Partner 0!