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
OK - so the usage pattern IU have (and most do I think) is:
only trusted users can use the service for sharing files
Anyone with the UUID link can come and get the file (with optional password added)
We actually have locations which can go in nginx of:
/fileshare - for people to come and get the files - needs to be completely unauthenticated
/ - needs to be authenticated
I would prefer Oauth (or sometyhing els ethat can use SSO with authentik)
I might be able to workaround it by specifying these two locations and for / passing to authentik and defining fileshleter as an app that certain user groups can access.
Anyone doing the same?
Better to recognise that we really don't want to open up fileshelter so any tom, dick or harry can share files (and fill up my disk or upload incriminating images to my server for example) but we do want to do that for recipients.
The text was updated successfully, but these errors were encountered:
OK - so the usage pattern IU have (and most do I think) is:
only trusted users can use the service for sharing files
Anyone with the UUID link can come and get the file (with optional password added)
We actually have locations which can go in nginx of:
/fileshare - for people to come and get the files - needs to be completely unauthenticated
/ - needs to be authenticated
I would prefer Oauth (or sometyhing els ethat can use SSO with authentik)
I might be able to workaround it by specifying these two locations and for / passing to authentik and defining fileshleter as an app that certain user groups can access.
Anyone doing the same?
Better to recognise that we really don't want to open up fileshelter so any tom, dick or harry can share files (and fill up my disk or upload incriminating images to my server for example) but we do want to do that for recipients.
The text was updated successfully, but these errors were encountered: