You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unless i made a mistake currently anonymous writes is not supported. Something like the following config will give you only read access to dir1and dir2
auth:
- '@/dir1:rw,/dir2:rw'
I'm facing a case where i put SSO before dufs (through k8s ingress and AWS ALB) and thus i don't need any kind of authentication.
I guess the same logic is applied for uploads, deltion etc...
Implement Suggestion
Allow end-user to setup RW access for anonymous error and enforce the default to avoid unwanted full open directory
It can also be done through an env variable like DUFS_ALLOW_ANONYMOUS_WRITES or DUFS_DISABLE_AUTH (because it's really what is is IMHO).
PS: thanks for the great tool ;-)
The text was updated successfully, but these errors were encountered:
for the record i also tried setting auth: [] in dufs.yaml and it's "worked". I have access in RW mode to all folder. So that can be a solution. But it allow full RW (not just the wanted dirs). In more complex scenario that can be a problem.
Specific Demand
Unless i made a mistake currently anonymous writes is not supported. Something like the following config will give you only read access to
dir1
anddir2
I'm facing a case where i put SSO before dufs (through k8s ingress and AWS ALB) and thus i don't need any kind of authentication.
I guess the same logic is applied for uploads, deltion etc...
Implement Suggestion
Allow end-user to setup RW access for anonymous error and enforce the default to avoid unwanted full open directory
It can also be done through an env variable like
DUFS_ALLOW_ANONYMOUS_WRITES
orDUFS_DISABLE_AUTH
(because it's really what is is IMHO).PS: thanks for the great tool ;-)
The text was updated successfully, but these errors were encountered: