Getting RootContainer for a User with limited permissions

Jashan

Hello there -

I'm accessing mediabin using it's exposed webservice. I authenticate myself using a mediabin server Id/pwd I'm given. FYI I do this outside teamsite session. So my webservice client is running and authenticates with mediabin server, completely outside of teamsite context.

ok. So the userId I have has access to only a specific container (say "MyContainer") I can read/write etc within this container. When I login using "MediaBin Thick client" I can see "MyContainer"

Now, from my webservice client when I call "GetRootContainer" I dont get "MyContainer". I believe I get the actual rootcontainer of mediabin server. And since I dont have permissions anywhere else, I cant really drill down using this root container I just got.

So my question is

"How do I get the rootContainer of a specific user?" Meaning, if a user is created with permissions only to a specific container, how do I get that root?

I looked various calls like (page numbers are from the SDK pdf) shown below, but all these calls need some dependent information. For instance, "GetContainerByPath" needs the rootContainerID...But I dont have my user's rootContainer !!
search_Containers - page 504
MBSearchCriteria - page 423
GetSearchableMetadata - page 355
GetContainerByPath - page 331
GetRootContainer - page 354
getContainerTree - page 465
MBContainerTreeNode - page 409
MBContainer - page 408



So how do I do it?

Thanks

Rick Poulin

I looked various calls like (page numbers are from the SDK pdf) shown below, but all these calls need some dependent information. For instance, "GetContainerByPath" needs the rootContainerID...But I dont have my user's rootContainer !!

There's no such thing as a "user's" root container. There's nothing to say that a user will ever have access to exactly one subtree -- it's all just ACLs in a repository. From a web service perspective, all the calls are relative to the root of the repository, regardless of which container the user actually has access to write. So, you would getRootContainer and then getContainerByPath to get to the user's container. If you're looking to dynamically figure out what that container is, you'll have to write your own code to resolve it, probably based on a combination of naming convention and/or business rules and/or resolving containers and checking permissions.

What you really want is a getWriteableContainersForUser() call, but last I checked (it's been a while), there's nothing that comes close to that so you'll have to write it yourself.