|
kevink responded: |
2015-07-07 10:30 |
|
|
blackhole612 responded: |
2015-07-07 10:47 |
I guess I wasn't exactly clear on what I want. I can transfer files between server using CyberDuck and dragging and dropping between the webdav folder and the other server, what I want to do is have it so that a user can login to their account on a remote server, similar to the Cloud module's sign in page, and be able to access their files integrated into the file manager, the same way that the remote Amazon S3 files are from the Cloud Module. I want to make it as seamless as possible for the end user, and so not having to install and setup CyberDuck or another SSH and webdav client would be ideal. |
|
kevink responded: |
2015-07-07 11:06 |
Ah, I understand. I recommend mounting the remove server's file system locally to the LabKey Server via NFS or Samba. I don't think it would be possible to mount a user's remote files locally without doing something like storing their credentials within LabKey Server. |
|
blackhole612 responded: |
2015-07-07 12:19 |
Okay, thank you. I don't have much experience with NFS or Samba, so I have one more question. If we do decide to do that, would users still log in to access their files? For example, if I wanted to access files I have stored on there, I would have to put in my username and password for the remote server? |
|
kevink responded: |
2015-07-07 12:52 |
Unfortunately, no, your individual user files would not be available. Usually, the remote files are a shared resource available to all users on the LabKey Server site or on a project-by-project basis. The file share will be mounted by the OS as a user that has read/write permissions to the files. To the server, the file share is just another file system and the server doesn't store any user credentials to the remote file share. |
|
|
|