Quantcast
Channel: Kaltura - Latest posts
Viewing all articles
Browse latest Browse all 7410

Security around Playlists

$
0
0

Hey all, it’s been a minute since I have posted. I hope things are well.

I’m trying to understand the playlist functionality in Kaltura Server. I have a potential requirement to implement user specific and “public” playlists in my Kaltura API app. I’d like to use the Kaltura Playlist functionality, but I’m unsure of a few things. (in this context “public” means available to all my applications users)

My main question is; Are Kaltura playlists owned by a specific user such that they can only “see” their playlists? It seems that the answer is no. Playlists are sort of a “global” thing in Kaltura.

If they can be user specific, how could one implement them in Kaltura? If it’s in the documentation, I’m just not seeing it and I just need to be pointed in the right direction.

This is against best practice, I know, but currently my API application uses an admin login to interact with Kaltura. I’d need to change this substantially if I was all of a sudden going to have user specific content on the platform. The documentation seems pretty clear on this, though I could use some clarification on user creation on the base platform vs user creation in KMC. They’re clearly not the same thing.

I hope this is a sufficient explanation on what I’m looking for. Thank you!


Viewing all articles
Browse latest Browse all 7410

Trending Articles