Don't create a local homedir - Restrict user to shared folders

[fostermi]

Is it possible to set a home directory for a user to a shared folder, specifically one that has been configured for an S3 backend? I'm looking at the Getting Started examples and the use case is very similar, with the exception of the requirement of a local home directory. Setting "homedir" to an empty string when using the Event Manager to automatically create users from an OIDC login, the application still wants to create or at least provide a local files system home directory of /srv/sftpgo/data/. The use case is access to files for collaboration to a specific group, possibly created elsewhere.

[fostermi]

At the very least I'd want to follow this example https://sftpgo.github.io/latest/initial-configuration/#usage-example where each user would have an "S3 virtual folder", but not be able to upload files to the local filesystem.

[fostermi]

Ah, in the example page, if you change the "Primary" group to use s3 as its filesystem with key prefix users/%username%/ this has the effect of setting their home directory to the s3 bucket configured in the group setting, even though if you look at the user's information, it still shows the user's home directory to be local storage at /srv/sftpgo/data/%usersname%/. Uploading a file from the UI at the users home directory ends up being on the configured bucket of the group. So in theory, you could use this to drop everyone's actual home directory to a common bucket/folder, it just wouldn't be reflected correctly in the user json representation of the user (homedir is still /srv/sftpgo/data/&username%).