Force KMC HTTPS, permission selection logic

[jpluijmers]

On our new Kaltura IX server I disabled Force KMC Https for our partner 102. However this did not have the intended effect. After doing some debugging I found the following lines in the PermissionPeer class (kmc module):

$permission = self::getByNameAndPartner($permissionName, array($partnerId, PartnerPeer::GLOBAL_PARTNER));

This includes the global partner (0) in the scanned permissions. However, in the getByNameAndPartner class the following sorting criteria is applied:

$c->addAscendingOrderByColumn(PermissionPeer::STATUS);

This in effect says: Always select Permission:ACTIVE over Permission:Blocked or Permission: Deleted. This way Active settings of the PartnerPeer::GLOBAL_PARTNER always prevail over partner specific settings. Is this intended behavior? And if it is, how do you change partner specific permissions?

I would suggest to add a second order column on partnerid, descending. This makes sure concrete partner rules are read first, while not breaking the multiple permissions case.

[jpluijmers]

After a quick search, this Behaviour also affects a lot of other locations.

[jpluijmers]

I implemented the following changes on my server #1725

This fixes some of the issue for me.

[jessp01]

Closing in light of #1725 (comment)