WebDAV: Serving different folder based on username

[Akusho]

Hello,
I'm using STFPGo for WebDAV, where I have two users with two folders.
When each user accesses the server with their credentials, each sees and interacts with a different folder. Is it possible in copyparty?

[9001]

no; due to the risk of security incidents, this is not possible. One example of the type of incidents I am concerned about: if you have logged in with a different user than what you thought you were, you might accidentally upload something into the wrong folder, perhaps somewhere unintended people can access.

one alternative that is offered in copyparty is to give each user their own volume --- this can be done automatically, https://github.com/9001/copyparty/blob/hovudstraum/docs/examples/docker/idp/copyparty.conf#L56-L93

[Akusho]

I believe this is what I had in mind, if I understood orrectly. Maybe my explanation was misleading.

In SFTPGOs docker compose I mount two separate folders into two locations inside the container. Each user, when logged in, sees and interacts only with that location without the ability to interact with the others.

Then when a software needs access to WebDAV, we use the same link, different credentials, and each have their own library to sync files to/from, without affecting the other.

[9001]

one example of what is possible:

[/david]
  /mnt/nas/homes/david
  accs:
    r: david

[/james]
  /mnt/nas/homes/james 
  accs:
    r: james

[/music]
  /mnt/nas/misc/music
  accs:
    r: james, david

[/music/david]
  /mnt/nas/misc/music/david
  accs:
    r: david

[/music/james]
  /mnt/nas/misc/music/james
  accs:
    r: james

if david logs in, he is able to see and interact with a folder named david on the server, and the folder "music", and "music/david". Likewise, james can see a folder named james, "music", and "music/james".

it is not possible to make /music itself point to different filesystem paths depending on who is logged in, due to the concern I mentioned.

[Akusho]

Got it. Thank you.
I'm circumventing this by routing through NPM to two different locations based on the initial domain.
i.e. webdav.mydomain/user1/ and webdav.mydomain/user2/
Each will be pointed directly to a different folder which only it has access to. Seems to work.