stapelberg/scan2drive

Consider supporting other authentication providers and sinks

Opened this issue · 0 comments

Currently, Google Drive is used both as a scan sink, and as an authentication provider.

This is convenient for users: you only need to log in once to grant permission to write scans, and to authenticate to scan2drive.

Theoretically, one could want to authenticate via tailscale and sink scans to amazon S3. This is currently not possible, and I’m not entirely sure yet how to re-architect the program to make it possible without losing the convenience of using one provider for both, authentication and storing scans.