Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do I use it for backend that requires token? #12

Open
stevefan1999-personal opened this issue Sep 1, 2020 · 7 comments
Open

How do I use it for backend that requires token? #12

stevefan1999-personal opened this issue Sep 1, 2020 · 7 comments

Comments

@stevefan1999-personal
Copy link

stevefan1999-personal commented Sep 1, 2020

It seems like I cannot go past the token generation, and I realized it is not just for GDrive but for all other backend types that requires token too like OneDrive, Mega and Box.

@stevefan1999-personal stevefan1999-personal changed the title How do I use it for Google Drive? How do I use it for backend that requires token? Sep 1, 2020
@Snake4life
Copy link

did you find a solution?

@Jancis
Copy link
Member

Jancis commented Nov 2, 2021

so the drive-token would not work? does it work with rclone?
https://rclone.org/drive/#drive-token

@PatrickHuetter
Copy link

@Jancis No, it's mostly an access and renew token (within a jwt token). Without this, you can't use dropbox or similar services that use OAuth2 since the token changes from time to time (gets renewed by rclone) and needs to be persisted somewhere.

@Jancis
Copy link
Member

Jancis commented Oct 17, 2022

Oh, sounds like chicken and egg problem where You need to mount a rwx storage on all rclone plugin pods and share the token, but You don't have any :)

I had some success with nfs-subdir-external-provisioner and a custom nfs server. If You mount a storage with rclone in it, You might have more or less the same system (but the storage is mounted in a single pod then). If You customize the nfs server, You could store and persist the token.

@dvcrn
Copy link

dvcrn commented Nov 2, 2022

  1. Do rclone config on your local machine
  2. Connect to the remote backend
  3. rclone config view
  4. Copy config into PersistenVolume

@PatrickHuetter
Copy link

This won't work stable since refresh tokens change and it might work the first time but won't after a while or after restarting the backend pod after a token isn't active anymore. The best case would be to you optionally a RWX volume OR a secret that can be written via k8s API by the pod. I think the best option would be to use an RWX volume since most storage providers already provide that.

@stevefan1999-personal
Copy link
Author

This won't work stable since refresh tokens change and it might work the first time but won't after a while or after restarting the backend pod after a token isn't active anymore. The best case would be to you optionally a RWX volume OR a secret that can be written via k8s API by the pod. I think the best option would be to use an RWX volume since most storage providers already provide that.

Agreed. We need a feedback mechanism.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants