Auth proxy for non-standalone backends like crypt/combine/union

Feature
1

It seems that return result of an auth proxy script is not enough to specify a non-standalone rclone backend. For example,

[encrypted]
type = crypt
remote = remote:/Encrypted

we need to have a config entry for the remote backend before we can create a crypt backend.

2

welcome to the forum,

not sure what you need help with, can you please explain with more detail?

what is stopping you from creating a new remote named remote

1 Like
3

Do you mean I can create another remote in my config file? I want the auth proxy to return a usable encrypted remote by itself.

The auth proxy seems to only support one remote in the return data. For example, the document rclone serve http says that we can return

{
  "type": "sftp",
  "_root": "",
  "_obscure": "pass",
  "user": "me",
  "pass": "mypassword",
  "host": "sftp.example.com"
}

this is only one remote of type sftp. In my example, I need at least two remotes.

1 Like